Update issue field post function gets saved twice in issue history if it is placed first in the list of post functions

Summary

Update Issue Field post-function: Remaining estimate will be set to 0 gets saved twice in issue history, if it is placed first on the list of post functions. As a consequence the equivalent value of Original time estimate for the issue is subtracted twice from Total Remaining Estimate in the Burndown chart

Environment

Cloud

Steps to Reproduce

1. Create a Scrum Board
2. Add post function on the Done transition: Remaining estimate will be set to 0
   • 
3. (Optional: you can add a screen on this transition to Log Work)
4. Transition the issue to Done

Expected Results

Setting the Remaining Estimate to 0 is saved once in issue history

Actual Results

Remaining Estimate to 0 is saved twice in issue history

Consequence of this is that the Remaining Estimate is subtracted twice from the Total Remaining Estimate in the Burndown chart

Notes

If there is work logged at the same time (using a screen in the transition), this change is ignored by the Burndown chart (it is not subtracted from the Total Remaining Estimate in the Burndown chart)

If there is work logged before the issue is completed, this value is subtracted from the Total Remaining Estimate the Burndown chart, plus when the issue is completed the equivalence of the Original Estimated Value for the issue is subtracted from the Total Remaining Estimate

Workaround

Don't use the post-function Remaining Estimate will be set to 0 and at this moment only log work to issues.

Notes: If the post function is placed at the bottom:

Remaining Estimate will be saved once in issue history.

However, if this is the case, only the actual logged work is subtracted from the Total Remaining Estimate in the Burndown chart and the Remaining time set to 0 is not taken into account (this is reported in JSW-6788)

For JIRA Cloud, the bug was fixed: JSWCLOUD-6788. So, it will create duplicate work in the Burndown chart.