-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
When transitioning a Jira work item from one status to another, if we have a transition screen with "Log work" and a post function to clear the "remaining time estimate" field to 0, then the burndown chart does not recognise the decrement to the "remaining time estimate" field.
Steps to Reproduce
- Should be in a classic project (sprint-enabled)
- Workflow can be simple: Todo → In Progress → Done. (Best to edit a new workflow then activate it)
- Whilst creating the "In Progress" → "Done" transition in this workflow, assign a screen to it. (The screen can be pre-existing).
- Modify this screen: add the "Log Work" field.
- In this "In Progress" → "Done" transition, add a new post-function: "Update Issue Field" - setting "Remaining Estimate" to 0. Publish the workflow with these changes.
- Add a new work item to the sprint, of an work item type that the screen is assigned to.
- Set the Original Estimate of this issue to 8h
- On the board, drop this issue into the Done column following the workflow, the screen should appear. In the screen modal:
- Log in 4h work into Time Spent
- Leave the Remaining Estimate field empty to auto-adjust.
- On transition completion, the post-function from the workflow should then automatically set the Remaining Estimate to 0h
Expected Results
The work item's remaining estimate should be 0 (since the post function has set the value to 0) after the transition.
Actual Results
The work item history section shows the reduction of Remaining Estimate to 0h, however, if we add this work item to the sprint as a scope change, we notice that the report accounts an increment of Remaining estimate to the value prior to the value "0" set by workflow post function.
Workaround
Use Jira automation instead of the Jira workflow post function to clear the "Remaining Estimate" field:
- Remove the post function from the workflow that clears the remaining estimate
- Add a Jira automation rule to set the remaining estimate value to 0m when a ticket transitions from any status to closed.
- duplicates
-
JRACLOUD-87871 The Burndown Chart does not consider JIRA post function when calculating Remaining Estimate
-
- Closed
-