Update burndown chart on each ticket update

[tote]

It would improve user experience a lot if we didn't have to wait for our cron job to run while the burndown chart gets updated. I think the ideal solution would be if the burndown chart was updated after each ticket update.

[Sam Bloomquist]

This is a good idea and should be fairly simple. I definitely should have done this to begin with to eliminate the whole need for the cron job. If I can get ahead on my "real job" duties in the next week or two, I'll try to make this change.

[andyg]

I definitely think this is a good idea.

Another thought (maybe requiring a new ticket), would be to optionally plot burndown points according to each change, but still on a daily axis. This way the plugin would be more useful in a modified scrum where estimates may be changed during a sprint. So if an estimate of a future ticket needs to be changed to show more work, and another ticket has some work completed (less effort remaining), the chart will show the increase and decrease instead of showing almost no change if they cancel each other out.

[anonymous]

Replying to andyg:

I definitely think this is a good idea.

Another thought (maybe requiring a new ticket), would be to optionally plot burndown points according to each change, but still on a daily axis. This way the plugin would be more useful in a modified scrum where estimates may be changed during a sprint. So if an estimate of a future ticket needs to be changed to show more work, and another ticket has some work completed (less effort remaining), the chart will show the increase and decrease instead of showing almost no change if they cancel each other out.

I second this idea.

[anonymous]

I'm so excited by this, I might just hack up the code myself to do it.

[Sam Bloomquist]

(In [2199]) refs #1248, #1219