Opened 10 years ago
user story #110 (new)
EndUser? should be able to better distinguish the summary progress of an issue, currently there is only Done and Not Done, but other states might be valuable, for example one or more stages are complete
Test Complete Size: | undefined | Test Complete Date: | |
---|---|---|---|
Documentation Complete Size: | undefined | Documentation Complete Date: | |
Acceptance Complete Size: | undefined | Acceptance Complete Date: | |
Reported by: | ja11sop | Owned by: | ja11sop |
Milestone: | Near Term | Component: | roadmap UI customisation |
Version: | Keywords: | ||
Cc: | Blocked By: | ||
Blocking: | Patch SVN Revision: | ||
Patch Trac Version: | not_applicable | ||
In Iterations: | None |
Description
EndUser? should be able to better distinguish the summary progress of an issue, currently there is only Done and Not Done, but other states might be valuable, for example one or more stages are complete.
A simple example would be that if there is at least one stage complete it might makes sense to change the summary box to, say, orange.
One way we might do this would be to associate a completion colour with a completion stage. The assumption here though would be that each stage would follow a linear progression. However this is not enforced by agile-trac (though often implied) and could therefore leasd to some interesting states. Having said that using this approach you could easily simulate the notion of a "at least one stage complete" by simply using the same colour for all stages. This could then be defaulted to orange (as an example) if no completion stage colours were specified.
Another consideration here is that it would be useful to identify closed stories as green (done) so that it is possible to ignore them when looking down the roadmap. Currently the summary box for such stories is white and therefore causes confusion among viewers who are unclear of the meaning. If these where green then it would be obvious that there is no outstanding work associated with the story.