-
Suggestion
-
Resolution: Unresolved
-
13
-
77
-
Problem Definition
Some reports (Velocity Chart, Sprint / Burndown Report) will show completed issues as not done or completed outside the sprint if the workflow is changed, where by the DONE status is unmapped from the board and not mapped to the last (right most) column on the board.
Jira business logic defines issues that are in the last column as complete. Any issues that aren’t in the last column on the board will be considered incomplete, irrespective of the status category mapped to that column.
This impacts the data that’s pulled through to reports.
Suggested Solution
Update Jira business / report logic where ‘Done’ is based on a status category or workflow and not column position.
Why this is important
Users with workflows that do not have ‘Done’ or ‘Done’ mapped to the last column will not be able to use reports for insights.
Hi everyone,
Thanks for your feedback on this problem. We appreciate the time that you took to help us be better.
Though not ideal in some cases, the behaviour in-product today is not a bug. Proposed improvements here are a feature request and have to be prioritized against other requests.
This is how reports and boards work in Jira:
- Reports and sprints are burning down issues based on the last column on the board.
- Our current reports are not built to report issues being done based on an issue’s entire lifecycle (done-done), but based on when each board’s work is done (last column), and the reports belong only to one board.
Expected Result
As a user, I update my board’s workflow. I don’t map the Done status to the last column on the board. What this means is:
- The Done status category is no longer associated with the last column on the board.
- The column with the Done status category is now in another position on the board (that’s not the last column).
- When using multiple boards, some boards intentionally don’t have Done in the last column. One board could be a QA board and the issue is only considered complete when it reaches the Releases board.
I expect the story points completed in the sprint will show as completed in reports.
Actual Result
The business logic in Jira defines issues that are in the last column as complete. Any issues that aren’t in the last column on the board will be considered incomplete, irrespective of the status category mapped to that column.
This impacts the data that’s pulled through to your reports.
- The velocity report will show 0 completed story points.
- The sprint report will convert previously completed issues with a Done status to their previous state such as To do or In progress.
To mitigate any problems, try this workaround:
- Go to Board > Manage workflow.
- Add the removed Done status to your workflow. Give the status the same name as previously used in your workflow and reports.
- At this stage, avoid adding any incoming transitions.
- Save and publish the workflow.
- From your board, navigate to the More actions (•••) > Board settings.
- In Columns and statuses, move the Done status to the rightmost column.
- Hit save.
- Your reports should behave as before. Add any incoming transitions to the status.
We’re using bugs to track any issues that prevent our features from being used as intended.
But we also understand and appreciate this escalation, and have converted this to a feature suggestion instead. This feature request will allow you to specify which status category is considered done on a board and in existing reports.
Please watch this Jira issue for future updates as we continue to work on improving reports.
This feature request requires a large investment and will be prioritized against other high-priority feature requests. On behalf of the Atlassian team, we take your feedback seriously and understand both the frustration and the urgency.
Please let me know if you have any further questions about this ticket.
Regards,
Ivan Teong
Product Manager, Jira Software Cloud
- is duplicated by
-
JSWCLOUD-17269 Velocity and Sprint report broken when the end status is changed in the worklfow
- Closed
- is related to
-
JSWCLOUD-17670 Closing Sprints and use of the 'Done column'
- Closed
-
JSWCLOUD-21497 Update Sprint Logic where 'Done' is based on a status category
- Closed
- relates to
-
JSWCLOUD-21805 Update Insights Logic where 'Done' is based on a status category or workflow
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...