user story #93 (sized)
EndUser? should have control over the display of the iteration work table, including what colums are shown and the default sort order
| Test Complete Size: | 5 | Test Complete Date: | |
|---|---|---|---|
| Documentation Complete Size: | 1 | Documentation Complete Date: | |
| Acceptance Complete Size: | 1 | Acceptance Complete Date: | |
| Reported by: | webpatser | Owned by: | ja11sop |
| Milestone: | Clean up of Plugin with Patch | Component: | iterations |
| Version: | Plugin 0.1.5 | Keywords: | priority |
| Cc: | Blocked By: | ||
| Patch SVN Revision: | Patch Trac Version: | 0.11.2 | |
| Blocking: | |||
| In Iterations: | 20 |
Description
The ticket order of an itteration is now based on their size.
Higher in the list means higher priority (Biggest points first)...
I think the severity should also be used to make the order.
So a small issue (in points) but with a higher severity (criticial) should be higher in the list than a big issue with a minor severity...
Change History
Have a look at the list of modified files related to this ticket.
Note: See
TracTickets for help on using
tickets.
