Modify ↓
Opened 17 years ago
Closed 15 years ago
#1292 closed defect (fixed)
Remove ticket from milestone after it started
| Reported by: | Owned by: | daan | |
|---|---|---|---|
| Priority: | normal | Component: | ScrumBurndownPlugin |
| Severity: | major | Keywords: | |
| Cc: | Trac Release: | 0.10 |
Description
The graphic becomes crazy if you remove a ticket from milestone after it started. It does not compute the hours removed from the estimative.
Attachments (0)
Change History (4)
comment:1 Changed 17 years ago by
comment:2 follow-up: 4 Changed 16 years ago by
For the burndown chart, removal of a ticket should have the same result as marking the ticket completed or the estimate set to zero. I don't think there is need to remove time from past datapoints.
comment:3 Changed 16 years ago by
| Owner: | changed from Sam Bloomquist to daan |
|---|
comment:4 Changed 15 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Replying to elecnix:
For the burndown chart, removal of a ticket should have the same result as marking the ticket completed or the estimate set to zero. I don't think there is need to remove time from past datapoints.
This seems a correct assumption to me. Historically this ticket was part of the sprint, so changing history seems a bit manipulative to me.
Note: See
TracTickets for help on using
tickets.
Looks like this is not a trivial task to remove estimated hours of removed task correctly from all burndown chart data for the current implementation. It is difficult to find out from which data points and how much hours should be extracted, as the removed task could brought its hours not from the beginning of the sprint, or some effors could already be added there...