user story #109 (new)
IterationUser? should be able to see the relative priority of items within an iteration that remains updated as stories are completed
| 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: | iterations |
| Version: | Keywords: | ||
| Cc: | Blocked By: | ||
| Patch SVN Revision: | Patch Trac Version: | not_applicable | |
| Blocking: | |||
| In Iterations: | None |
Description
IterationUser? should be able to see the relative priority of items within an iteration that remains updated as stories are completed.
This should really work in a fashion similar to how milestone priorities are handled. Initially all stories in the iteration would have the same priority, but some could be assigned a higher relative priority.
As stories are completed the remaining stories should then have their priorities adjusted. Not that this should not be confused with a tickets's priority field and so we might need to think of a better name for this.
Change History
Have a look at the list of modified files related to this ticket.
Note: See
TracTickets for help on using
tickets.
