userstory #16 (closed: DONE)
EndUser? will be able to observe and appreciate better the presence of undecided sized tickets in a milestone and the potential effect on progress
| Test Complete Size: | 5 | Test Complete Date: | 07/19/2008 |
|---|---|---|---|
| Documentation Complete Size: | 0 | Documentation Complete Date: | |
| Acceptance Complete Size: | 0 | Acceptance Complete Date: | |
| Reported by: | ja11sop@… | Owned by: | |
| Milestone: | Patch Against Trac 0.11 | Component: | release planning |
| Version: | Keywords: | ||
| Cc: | Blocked By: | ||
| Blocking: | Patch SVN Revision: | ||
| Patch Trac Version: | |||
| In Iterations: | 7 |
Description (last modified by ja11sop@…) (diff)
EndUser? will be able to observe and appreicate better the presence of undecided sized tickets in a milestone and the potential effect on progress.
EndUser? ticket workflow could include an undecided state to unsized tickets allowing such ticket status to be explicit.
For example a basic flow might be,
undecided_new -> new -> assigned -> accepted -> closed
or
undecided -> unassigned -> assigned -> accepted -> closed
where new tickets are undecided + unassigned.
It may make sense to have an undecided size block ticket state from moving to accepted.
It may simply be sufficient to display undecided sized tickets using a different, but obvious, colour on the roadmap page.
Change History
Have a look at the list of modified files related to this ticket.
Note: See
TracTickets for help on using
tickets.
