userstory #33 (sized)
EndUser? will have the due date status reflect the expected completion date to make it more useful
| Test Complete Size: | 3 | Test Complete Date: | |
|---|---|---|---|
| Documentation Complete Size: | 0 | Documentation Complete Date: | |
| Acceptance Complete Size: | 0 | Acceptance Complete Date: | |
| Reported by: | ja11sop@… | Owned by: | |
| Milestone: | Clean up of Plugin with Patch | Component: | release planning |
| Version: | Keywords: | ||
| Cc: | Blocked By: | ||
| Patch SVN Revision: | Patch Trac Version: | not_applicable | |
| Blocking: | |||
| In Iterations: | 19 22 23 |
Description (last modified by ja11sop@…) (diff)
EndUser? will have the due date status reflect the expected completion date to make it more useful
For example if the due date is the 17th of June 2008 and the expected completion date is the 23rd of August and the current date is the 20th of June it might say:
3 days late (due DD/MM/YYYY), expected 5 weeks late
Due DD/MM/YYYY - 3 days late, expected 5 weeks late
others might be
Due in 1 month (due DD/MM/YYYY), expected 1 week late
Due in 2 months (due DD/MM/YYYY), expected 2 weeks early
Was due DD/MM/YYYY - completed 1 week early
In fact we would want to consider that we have an expected date range and that starts to complicate things a little.
Change History
Have a look at the list of modified files related to this ticket.
