Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Eoin
Product Manager, Jira Cloud
Current behaviour:
The right-most column in the Jira Active Sprint Board is used to depict what issues/tasks are complete.
Issue:
Anything outside of this column is considered incomplete when a user tries to close a sprint and those tickets are forced out of the sprint.
Repercussions:
This means that if the board is configured to have 'Done' tickets in a different column, they are then added into another sprint or to the backlog when a user tries to close the current sprint, despite actually being completed. To get them back into the correct sprint, someone would then have to identify the tickets and bulk update them. (Note - it actually currently appends a new sprint onto them, so they end up with Closed Sprint and Next Sprint... e.g. 'Sprint 1, Sprint 2' (, Sprint 3, Sprint 4, etc).
Forcing all Jira admins to configure their workboards so that the right-most column holds all completed task statuses seems to go against principles of flexibility and autonomy, as it doesn't allow teams to set up their workflows to suit them best.
Example:
We have a Task board, with statuses in this order:
TO DO - WAITING - IN PROGRESS - DONE - CANCELLED
Cancelled is to the right, so that it's out of the way but still visible.
Even if we put the Done column to the right, the cancelled items would be forced to move to the next sprint when we try to close this sprint.
We don't want to add both statuses to the same column.
Suggested solution:
Associate a Status Type (Complete vs Incomplete) with each Status, rather than using a single column to determine this.
Allow admins to specify/configure this value against each status.
- is duplicated by
-
JRACLOUD-85722 Update Sprint Logic where 'Done' is based on a status category
- Closed
- is related to
-
- Closed
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWCLOUD-17670] Closing Sprints and use of the 'Done column'
This is awful design. We have multiple done statuses which should resolve our issues but only the right-most column actually counts as done with existing functionality. We tried to get around this by using swimlanes but there are no swimlanes in team-managed projects so we're just stuck with not being able to reflect our workflow.
My dev teams have a Canceled status and would like this also to be counted as Done so it is not carried over from sprint to sprint. Please work on this issue!
We have encountering similar issues, and it's confusing to our users. Is it possible to determine completed issues based on "status category", so that no completed issues are being moved to the next sprint when completing the current sprint. Cheers.
This is a bug of design. The "done" category should be the marker of tickets completion
I faced this problem too and doesn`t make sanse at all. In my opinion this should be treated as bug.
This is really an unexpected issue when it bites you. We can be fairly certain that no one expects having "Done" issue statuses, that effectively close issues, and then have a totally new "complete" concept that requires implicit behavior from column ordering.
"Infra Automation" Project requires the "Cancelled" issues to be closed within the same Sprint and not to be moved in future sprints or backlog.
We want to set expectations of the improvements that will come in the next 12-18 months, and this suggestion is not something we are considering in that timeframe. Company-managed projects will continue to use the last column on the Board to drive definition of done from a reporting perspective.
In the longer term future, this is something we'll revisit.
Thank you for watching, voting, and commenting on this issue.