#8695 closed enhancement (fixed)
burndown graph should not finish with milestone's 'due' date but with 'completed' date
Reported by: | falkb | Owned by: | osimons |
---|---|---|---|
Priority: | normal | Component: | EstimationToolsPlugin |
Severity: | normal | Keywords: | |
Cc: | osimons | Trac Release: | 0.12 |
Description
I have a burndown graph
[[BurndownChart(milestone=Foo, startdate=2011-03-10)]]
in a milestone that was not finished until the 'due' date of the milestone. Unfortunately, I cannot see the development of the remaining hours from that 'due' date until today, because the Burndown graph does end with the 'due' date.
That is why the burndown graph should display the range until the 'completed' date of the milestone, maybe in a red colour between 'due' and 'completed' date to mark it as overdue.
Attachments (1)
Change History (6)
comment:1 Changed 14 years ago by
Owner: | changed from Joachim Hoessler to osimons |
---|
Changed 14 years ago by
Attachment: | t8695-no_due_in_past-r10048.diff added |
---|
Patch to not use milestone 'due' if it is in the past.
comment:2 follow-up: 3 Changed 14 years ago by
Patch works! Thanks.
P.S.:
Replying to falkb:
... the burndown graph should display ... in a red colour between 'due' and 'completed' date to mark it as overdue.
Or maybe a vertical red line at 'due' date to show we've exceeded the limit
comment:3 follow-up: 5 Changed 14 years ago by
Replying to anonymous:
Or maybe a vertical red line at 'due' date to show we've exceeded the limit
This is really a separate request, as the plugin does not yet have any means of tagging custom events or otherwise drawing anything other than the line. #4131 and #4217 also requests some variation markings, so please transfer your ideas to one of those tickets or create a new ticket for it. This particular 'due' vs 'completed' vs 'today' as value for enddate
is just one possible use for such a general marking-feature.
I'll get the patch for enddate
calculation committed, though.
comment:4 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
(In [10082]) EstimationToolsPlugin: Don't use milestone 'due' date if it falls in the past, as data between 'due' and 'today' wont then be charted.
Oh, I see - it will only display the time between 'due' and 'completed' AFTER the milestone is actually completed. So when checking 'due' we should not actually use it unless it is a timestamp in the future. If 'due' is in the past, we just use the current 'now' as
enddate
.Makes sense. Should be a simple patch. I'll look into it.