Christopher Lenz wrote:
Am 10.03.2006 um 11:25 schrieb Christian Boos:
Christopher Lenz wrote:
Am 10.03.2006 um 10:05 schrieb Christian Boos:
..
I'd like to have at least the progress bar in the core Trac (see
ticket #1084),
in order to match FlySpray's percent complete functionality. See:
http://flyspray.rocks.cc/bts/ for how it looks in the overview, and
e.g.
http://flyspray.rocks.cc/bts/task/612 for how it looks in the
ticket view.
Doesn't make sense to me to include a widget if we don't actually
support any kind of "percent complete" for tickets.
Of course. Should I interpret your statement as "we're not going to
implement #1084"?
It's set to wontfix, no?
Ah yes :P)
It has been on my Todo list for a while, that's why I didn't bother to check
... and as you know, the ticket status/resolution is not _that_ apparent
anymore
(http://projects.edgewall.com/trac/ticket/1990).
It would be nice if Alecs workflow work enabled such a feature to be
provided as a plugin, of course.
Ok, let's see if that can be done as a plugin.
Besides, even if that feature doesn't make it in the "core"
properties of a ticket,
the progress bar "widget" would still be useful in order to allow a
custom ticket
field to use it (and simulate the #1084 functionality).
I'm reluctant to add code that doesn't get used with the default
install without adding plugins. If at some point in the future there
are 15 different field provider plugins that all come with slightly
different flavors of progress bars, we should consider providing a
builtin field type, but I think that's an unlikely scenario.
OTOH a kind of "scale" widget, of which the percent complete is only
a particular case, is certainly general enough to warrant inclusion within
the core.
Same can be said for a date field:
http://projects.edgewall.com/trac/ticket/1942
http://projects.edgewall.com/trac/ticket/2151
-- Christian
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
