Change method for computing burndown

[adean@…]

Opening ticket after discussion started here : ​http://stuq.nl/weblog/2008-12-25/scrum-burndown-plugin-191-released#comment-5468

The plugin currently calculates burndown as 'hours estimated for ticket - hours spent on ticket'. Per Scrum best practices, burndown should be only the 'estimated hours', and should not involve the actual hours spent on the task.

[Alex Dean]

Quick patch. Quick test on sqlite only.

[anonymous]

Some people may want to preserve the original estimate, thus having the fields 'original estimate', 'estimated hours left' and 'hours spent on ticket'.

• 'estimated hours left' would be used for the burndown
• 'hours spent on ticket' for billing or tracking
• 'original estimate' would be compared to 'hours spent on ticket' after it's completed to improve future estimates.

I currently do burndowns in Excel and I have the fields estimate and percent completed with percent completed x estimate used for the burndown. I'm thinking about moving us to trac for the burndowns and in that case the above three fileds would be what I need.

This would not change the logic of the patch above, just split up the estimate field in one original and one that you update while working on the ticket.

[adean@…]

The 'original estimate' is always available. It is the first 'estimatedhours' record for the ticket in the ticket_change table.

select * from ticket_change where field='estimatedhours' and ticket='20';

It may be more convenient to store the original estimate separately. Just pointing out that it isn't strictly necessary.