-
Suggestion
-
Resolution: Done
-
29
-
We shipped this today! Let me know if you have any questions or concerns.
Thank you,
Bryan Lim
Product Manager
Problem definition
Status categories in next-gen projects will follow the columns' orders in the board. For example, the left-most column or status in the board will be using "To Do" category, the right-most column/status of the board will be using "Done" category and other columns/statuses will be utilizing the "In Progress" category.
Currently it's not possible to customize these categories, for example to set the category of multiple statuses/columns to "Done".
Suggested resolution
Provide the ability to customize the category of statuses in next-gen projects.
- is related to
-
JSDCLOUD-9534 New ticket is not shown in the queue when it's transitioned to newly created status
-
- Closed
-
-
- Gathering Interest
- relates to
-
- Closed
-
- Closed
[JRACLOUD-85675] Multiple done statuses (with multiple columns) and the ability to map multiple statuses to one column on the board
marcel54 A Board is a representation of a team’s work and sprints & reports assume work moves from left to right on the board. How would you feel if I asked you map your "Discarded" status to the right-most column with the "Done" status on the board?: https://community.atlassian.com/t5/Jira-articles/New-Features-Additional-Done-Statuses-Map-Multiple-Statuses-per/ba-p/1638591
@blim
I've added a small test-project with a Scrum template as well and currently see this behaviour:
- add a new "Discarded" status that resembles a "Done" state.
- add a new Discarded column (which is not the most right-most column)
- start a sprint, add 2 tickets to the discarded column, 1 to the done column
- finish the sprint
What happens is that the 2 discarded tickets get moved to the next sprint, but they should not show up anymore.
@blim, I tested this as well on our next-gen project. From what I can see there is still a little bug.
I had the DONE status and created another ARCHIVED status which was of category "Done"
It automatically put it into a separate column which was last on the board but the Done stories where not taken up as resolved stories. This was highly visible in the report charts.
To solve it I've put the DONE and ARCHIVED status in the same column.
c6a1f1453e13 Are all your Done statuses grouped to the last column?
18adf88b2ac3 in next-gen, all done statuses are marked as resolved 
(for now)
@kajsa @davidreinberger
https://confluence.atlassian.com/jirakb/jira-issues-need-a-resolution-826873869.html
because your done status doesn't have a "resolution type = done" attached to it
Sprint burndown chart does not take other done statuses in to consideration unfortunately... Moved quite a chunk of issues yesterday in to a Done Status column and it did not change the burndwon chart... This is exactly why we wanted another done status... Is there a setting that we need to change?
8c2662fa7196 Strange. Can you send me screenshot(s)? bryan.lim@atlassian.com
Why do the other Done statuses still show as Unresolved in the Confluence Jira plugin Resolution column?
Won't this then influence the velocity of sprint if both status are mapped to the same column?
Currently what we do for tickets, that we won't do anymore/discard:
1. put them in the discard column
2. end the sprint
3. the tickets in the discard column will move to the next sprint
4. go to the backlog, move all discarded tickets to the backlog
5. reload the page and the discarded ones will be gone.