/~mbooth/BugzillaEmail.png
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/210#comment:5
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
: | Keywords:
--+
Comment (by gjm):
I have brought this up in the bloodhound-dev list.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/210#comment:6
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue
: dashboard|Version:
Resolution: | Keywords: starter
--+---
Changes (by peter):
* owner: peter = nobody
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/95#comment:4
Apache Bloodhound https://issues.apache.org
|Version:
Resolution: | Keywords: starter
--+--
Changes (by gjm):
* milestone: Release 2 =
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/95#comment:5
Apache Bloodhound https://issues.apache.org/bloodhound
Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
they are inconsistent with the current design and were never
designed for mouse-operation. Not even Apple uses them in their desktop
software, apart from a handful exceptions.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/146#comment:17
Apache Bloodhound https://issues.apache.org/bloodhound
/ticket/212#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
' is highlighted. I'm proposing that the whole row in the
change history should be highlighted instead with the yellow background.
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/212#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue
on whether we need to stop the setup when either is
missing so perhaps it would be better to output a warning saying that the
repository specification was ignored.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/154#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache
in the footer but I assume it would be
better to be in there as part of the base template.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/13#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
:
Resolution: | Keywords: starter
--+--
Changes (by gjm):
* status: new = assigned
* owner: gjm = nobody
* keywords: = starter
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/13#comment:4
Apache Bloodhound https
designed for mouse-operation.
ok
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/146#comment:18
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
that solution]
is not enough could you please mention whether extending that horizontal
bar will work ?
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/213#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
are :
- Use plain old checkboxes
- Inplace editor for ticket radio fields . Please take a look at image
below .
Feedback is welcome
[[Image(bh_theme_x_71_ticket_inplace_radio.png, width=600)]]
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/146#comment:19
Apache Bloodhound
Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Password reset for user for user jure
--
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Password reset for user for user jure
--
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
|Version:
Resolution: | Keywords: starter
+---
Changes (by jure):
* owner: nobody = jure
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/154#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache
...
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/154#comment:4
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
|Version:
Resolution: | Keywords: starter
+---
Changes (by jure):
* status: assigned = accepted
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/154#comment:5
Apache Bloodhound https://issues.apache.org/bloodhound
: Release 2
Component: dashboard |Version:
Resolution: | Keywords:
+---
Changes (by jure):
* status: assigned = accepted
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/190#comment:2
Apache Bloodhound https
/203#comment:13
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
div.trac-resizable { width: 100%; }
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/211#comment:4
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
failed for this input but
this will be tracked by a different ticket.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/204#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
return self.format_summary(*args)
File /home/bloodhound/bh/bloodhound/trac/trac/ticket/api.py, line 561,
in format_summary
summary = type + ': ' + summary
}}}
We should check if Trac has already fixed this.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/215
Apache Bloodhound https
://issues.apache.org/bloodhound/wiki/BloodhoundContributing
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'BloodhoundContributing' page.
If it was not you, please
be nice if it would ''';)''' . Hence I invite you
to follow the discussion in there by adding your e-mail addresses to Cc
list .
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/216#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating
Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
|Version:
Resolution: fixed | Keywords: starter
+---
Changes (by gjm):
* status: accepted = closed
* resolution: = fixed
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/154#comment:7
Apache Bloodhound https://issues.apache.org
are to be removed in #182
(which, incidentally looks pretty good but probably needs to be applied
after this) and any changes associated with the date display in #176.
ok
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/177#comment:22
Apache Bloodhound https://issues.apache.org/bloodhound
of the first line
at this point? That problem does not appear either.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/177#comment:23
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
implementation using a particular mobile
device ? What are the results ?
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/217#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
leaving the right hand part of the comment as
{{{.offset2}}} and removing a whitespace change.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/177#comment:26
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
design|Version:
Resolution: fixed| Keywords:
--+---
Changes (by gjm):
* status: accepted = closed
* resolution: = fixed
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/177#comment:27
Apache Bloodhound https
/bloodhound/ticket/146#comment:21
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
://issues.apache.org/bloodhound/milestone/Release%202
The %20 does not help to make it more readable.
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/219#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
: | Keywords:
+
Description changed by jdreimann:
Old description:
,, ... via ''Bloodhound'' quick create ticket dialog,,
New description:
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/220#comment:1
Apache Bloodhound https
Component: dashboard |Version:
Resolution: fixed | Keywords: starter
+---
Changes (by jdreimann):
* milestone: = Release 2
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/205#comment:5
Apache Bloodhound https://issues.apache.org
(2 matches).
It should really show (1 out of 3 matches) on page one and (2 out of 3
matches) respectively.
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/221#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
existing
milestone )
1. Use `+` rather than `%20` in URLs (... in code ...)
jftr
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/219#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
something like
[http://addyosmani.github.com/jquery-ui-bootstrap/ jQuery Bootsrap] to
make it look Bootstrap-y .
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/222#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
necessary to document the approach used to
install in-place editors , and handle related form submissions .
,, ... via ''Bloodhound'' quick create ticket dialog,,
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/224#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound
/ticket/223#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
] have
to be installed for tablets and smartphones .
,, ... via ''Bloodhound'' quick create ticket dialog,,
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/223#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
field'' and ''cc'' in attached screenshot).
Feedback is welcome .
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/206#comment:9
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
,,
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/223#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/174#comment:10
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
://issues.apache.org/bloodhound/ticket/146#comment:23
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/206#comment:10
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
/ticket/206#comment:11
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
: https://issues.apache.org/bloodhound/ticket/206#comment:12
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
)]]
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/174#comment:11
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/174#comment:12
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
with the site or even read it - so
it's a constant case of panning and zooming to get anything done.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/217#comment:4
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
://issues.apache.org/bloodhound/ticket/206#comment:13
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
to the fact that this will save us from some
headaches for similar issues happening under different circumstances for
which a quick hack is not available .
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/27#comment:4
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache
|Version:
Resolution: | Keywords:
--+-
Comment (by olemis):
I recently took over maintainership of that plugin .
;)
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/27#comment:6
Apache Bloodhound https://issues.apache.org
for me ...
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/174#comment:13
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
: | Keywords: css starter
+-
Comment (by gjm):
As mentioned on bh-dev, I don't think that jQuery Bootstrap is appropriate
at the moment.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/222#comment:2
Apache Bloodhound https
on my local testing environment . Active
scroll spy item is not highlighted.
I think that's a small enough issue that we can raise a separate ticket to
look at it again later.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/174#comment:14
Apache Bloodhound https://issues.apache.org
to actually improve it. I
suggest we do this the same way we disabled others in #39.
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/226#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
|Version:
Resolution: | Keywords: Activity widget css
+-
Changes (by olemis):
* owner: olemis = gjm
* status: accepted = assigned
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/226#comment:4
Apache Bloodhound
dialog,,
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/228#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
/%3C070.12e315d1fb01dea5055b33eda063802b%40incubator.apache.org%3E
this email]. My suggestion is that the email should contain only the diff
information.
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/229#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating
/bloodhound/ticket/206#comment:15
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
the
navigation it provides.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/174#comment:15
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
: | Keywords: bootstrap, ticket, scrollspy
--+--
Changes (by gjm):
* owner: olemis = gjm
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/174#comment:16
Apache Bloodhound https://issues.apache.org
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
from an implementation perspective
that's why I ask
''';)'''
Yes, I'd be happy with this functionality in every place that supports
WikiFormatting.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/231#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache
URL: https://issues.apache.org/bloodhound/ticket/232#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
: | Keywords: starter
--+-
Changes (by jdreimann):
* keywords: = starter
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/232#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue
/236#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
| Keywords:
+---
Changes (by gjm):
* status: new = closed
* resolution: = fixed
Comment:
r1398842 fixes in line with the patch above
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/236#comment:2
Apache Bloodhound https
: | Keywords: vendor
+---
Comment (by gjm):
r1398858 updates vendor/current to trac 1.0 tag (trac:r11307)
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/159#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache
. ~~
Something like GMail or Google+ attachments has been suggested indeed in
attached mockup.
,, ... via ''Bloodhound'' quick create ticket dialog,,
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/195#comment:5
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache
|Version:
Resolution: | Keywords: versioncontrol vcs
--+
Changes (by olemis):
* owner: = olemis
* status: assigned = accepted
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/162#comment:5
Apache Bloodhound
/bloodhound/ticket/237#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
(admin panels) , and #88 (tables) seem to be applied even if another theme
is activated .
,, ... via ''Bloodhound'' quick create ticket dialog,,
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/237#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound
a plugin hosted by t-h.o
and I noticed that ticket activity was always empty after disabling
`multiproduct.ticket.ProductTicketModule` class . We need to dive deeper
to figure out what's wrong .
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/238
Apache Bloodhound https://issues.apache.org
: | Keywords: vendor
+---
Comment (by gjm):
r1398864 tags vendor/current to vendor/1.0
r1398968 merges trac 1.0 into trunk/trac
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/159#comment:4
Apache Bloodhound https://issues.apache.org
),
'perm': rd._get_perm,
'session': rd._get_session,
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/239
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
New user registration for user habakuk
--
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
:
Resolution: | Keywords:
+---
Changes (by gjm):
* milestone: = Release 3
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/239#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue
stream;
tx = Transformer('body')
def add_classes(classes):
}}}
Isn't it about time to commit this modification ?
Any other comments | suggestions are welcome .
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/162#comment:6
Apache Bloodhound https
Deleted User for user gjmtest
--
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
New user registration for user gjmtest
--
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
above is a bit too protectionist, immediate
upload certainly seems to me to be inconsistent with the conclusions I
believe we have come to about inline editing on the same page.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/195#comment:8
Apache Bloodhound https://issues.apache.org
as inspiration :)
See ticket #240.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/223#comment:10
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
/incubator/bloodhound/trunk/doc/html-
templates/ticket.html ticket view html mockup].
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/240#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
://issues.apache.org/bloodhound/ticket/240#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
:
Resolution: | Keywords:
+---
Comment (by olemis):
In the meantime attached patch will upgrade to 2.1.1 . Needed for #195 .
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/220#comment:3
Apache Bloodhound https://issues.apache.org
#comment:9
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
ticket dialog,,
--
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/243#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
: | Keywords: WikiFormatting preview
--+
Changes (by olemis):
* keywords: = WikiFormatting preview
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/243#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound
, is_inline in
TypeError: unsupported operand type(s) for /: 'Undefined' and 'int'
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/244
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
: | Keywords:
+--
Changes (by jure):
* owner: nobody = jure
* status: new = assigned
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/244#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound
: | Keywords:
+--
Changes (by jure):
* status: assigned = accepted
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/244#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
| Keywords:
+
Changes (by jure):
* status: accepted = closed
* resolution: = fixed
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/244#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound
).
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/243#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Component: dashboard |Version:
Resolution: fixed | Keywords: starter
+---
Comment (by rjollos):
Ticket has been filed in Trac, trac:#10923.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/205#comment:6
Apache Bloodhound https
601 - 700 of 1949 matches
Mail list logo
