Opened 18 years ago
Last modified 16 years ago
#637 new enhancement
Have a capacity line in the chart when the due date of a milestone is set
Reported by: | Olger Warnier | Owned by: | daan |
---|---|---|---|
Priority: | normal | Component: | ScrumBurndownPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.10 |
Description
Hi,
I made some additions to your ScrumBurndownPlugin in order to support a capacity line. It draws an additional line when the milestone due date is set.
(calculate the difference between start and due date, and adds the line with a seperate array of points)
If you're intrested I can provide a patch. (this will include some additional fixes, like setting the current_estimate to 0 when a ticket is closed (in the burndown_job) and not displaying a chart when there is no data.
Attachments (2)
Change History (9)
comment:1 Changed 18 years ago by
comment:2 Changed 18 years ago by
Great, the patch for the capacity is attached. With regards to the ticket closure I see you have created a ticket:638. I have some notes you might consider but these will be added there.
The patch expects the burndown_job to run every day (not skip weekends) as the capacity is calculated using the milestone start and due date. (you will see that in the code)
There is a small hack in the line.js that is used to draw the lines, it now uses the colors given via the burndown.cs
Feel free to change it to your own style/insight...
Changed 18 years ago by
Attachment: | capacity-diff.patch added |
---|
capacity calculations patch file (svn diff)
comment:3 follow-up: 4 Changed 18 years ago by
Status: | new → assigned |
---|
For this one, I plan to add some UI (probably integrated with the WebAdmin plugin) for selecting which days of the week are workdays and which aren't. That way, the capacity line will actually reflect an 'ideal' or 'planned' burndown and will be more useful as a comparison for whether the real work is on schedule. I could just use non-weekend days for the capacity, but some people schedule to work on weekends. By making it configurable, it should suit everyone's needs a little better.
comment:4 follow-up: 5 Changed 18 years ago by
When do you plan to integrate changes from this ticket and make another delivery of ScrumBurndown plugin ? I ask you this because i can not integrate succesfully the changes from capacity diff patch.
comment:5 follow-up: 6 Changed 18 years ago by
Replying to aragorn185:
When do you plan to integrate changes from this ticket and make another delivery of ScrumBurndown plugin ? I ask you this because i can not integrate succesfully the changes from capacity diff patch.
I don't know. I'm currently very swamped with work and the starting of two side businesses.
comment:6 Changed 18 years ago by
Replying to sambloomquist:
I don't know. I'm currently very swamped with work and the starting of two side businesses.
Maybe you should try to hand off ownership of burndownplugin to someone else? Otherwise, looks like we should migrate to ScrumPlugin....
Changed 18 years ago by
Attachment: | capacity01.08.10.patch added |
---|
Capacity patch against 01.08.10 . This is just applying the original patch to the current code "manually" I plan to do more work on this
comment:7 Changed 16 years ago by
Owner: | changed from Sam Bloomquist to daan |
---|---|
Status: | assigned → new |
Sure, a patch submission would be great and much appreciated. This is one of the things I had planned, but haven't got around to yet.
I don't think I would include the part about setting the current_estimate to 0 when a ticket is closed because that would open up the possibility of closing a ticket in which time_spent is greater than current_estimate, which would cause negative balances on the chart. Instead, I'm planning to include some validation code that doesn't let you close a ticket unless the current_estimate and time_spent are equal.