Jira Agile Burndown Chart not decreasing after remaining estimate is set to zero through a workflow.

[Pablo Arango]

We are facing a rare problem here. We have a workflow that sets to zero the remaining estimate of issues that are closed before the total estimated time expected. So in the burndown chart this should be reflected with a decreased time for that issue, but its not happening. It does work well when someone logs work and selects to reduce the remaining estimate.

Any suggestion?

[Charles NICOLAS]

The solution seems to be here: https://community.atlassian.com/t5/Jira-Software-questions/RTE-in-a-Burndown-Chart-is-not-zero-at-Sprint-End/qaq-p/840902

[Pablo Arango]

Thanks Radu, but it's not a solution, we would have to pay for it, and its not worth for the moment. Plus... Jira Agile itself should be capable of doing it right.

[Radu Dumitriu]

Setting the RE is not like setting any other fields. My immediate guess is that plugin you're using is messing the 'remaining estimate'.

To confirm that:

1. Install JJupin (I know we're doing it right)

2. instead of that postfunction, add a JJupin postfunction with the script:

estimate = 0;

3. test it, see if this is still there

4. If yes, there's another issue going on.

If not, file a bug on the plugin.

5. Uninstall JJupin.

Of course, do it on a test system.

[Pablo Arango]

Through the workflow... in the post conditions you can select set RE to a value in the "Update issue field" function of a transition.

[Radu Dumitriu]

How do you set the RE to 0 ? Using some plugin?