I need to add two Done columns in Scrum Board as one of my status is closed one and for Burndown to work ideally it should be in Done Column but i wont be able to see both the columns separately in Active Sprint board as i dint get any option to add multiple Done Columns.
Also, if you do add another "done" type column, it won't be classed as "done" unless it is the last column on the right-hand side. Jira only looks at the very last column on the board to define "done".
Hi @shivam chhouda,
Each column on a scrum board needs to be mapped to at least one status. Once a status is mapped to a column it cannot be shared. To have more than one Done column you would need another Status added to your issue's workflow.
Separately, I would advise against adding more than one Done status and column to a scrum board as this may screw reporting and sprint closure if not managed correctly.
Hope this helps
How to bypass that ? such a stupid limitation, as always
It's not in the slightest bit "stupid" - it is a clear, simple and unarguable definition of done, as Agile (and, for that matter, Waterfall) processes strongly recommend.
The "bypass" is to put all your end status into the last column.
I don't disagree with the definition of Done, I'm just surprised that you have to choose the "status" of a column (to do, in progress or done) - and no matter the status that are in this column - which defines the color of the column (white, green, blue) and therefore its status REGARDING the sprint, but even tho you select Done the column stays green if it's not at the very right as you said, which is actually a VERY ODD LIMITATION that serves no real purpose.In my case I need to have a visual differentiation on the board between multiple status, all being resolved/done tickets, all I need is to split those into 2 columns but I can't have that, otherwise only half of them will be registered as Done when completing the sprint.So yeah ofc I "bypassed" it by putting everything in the last column but that's not what I call bypass, it's simply renouncing to the "feature" I need, if we can even call that a feature.If you can't see that then... sorry ^^
I'm running into this issue as well.
I have a "Done" column and a "Rejected" column.
Both have been set as "marked as done" in the workflow - yet only the far right column is considered to be "done" when I close the sprint.
Why can I create a workflow with multiple "done" columns but the sprints only treat the far right column as done? The UI is contradicting each other.
It's like the developers who built the "Complete Sprint" button never had a conversation with the developers who built the workflow functionality.
You need to map both status into the column that tells Jira that the issue is done.
You are not creating a workflow with multiple done columns, it has multiple done status. You should map those done status into the done column.
There's a point here that a lot of people miss - your board is a representation of what the team is working on. It is NOT for tracking stuff outside the team. The "done" column means "team has done what it needs to, and hence has no further interest". You don't need multiple "done" columns - issues in there are done, the team doesn't need to worry about them any more. The exact reason they don't need to is utterly irrelevant.
It's like the developers who built the "Complete Sprint" button had a conversation with the teams using it and kept is as simple and clear as possible.
What you describe is EXACTLY what I'm trying to do - I just want to have different labels associated with "done."
The Jira UI is contradictory. It says that something is "done" but doesn't actually mean "done." I shouldn't have to perform Google Searches to figure out that done isn't done and I can label something as done without it actually getting treated as done.
It is NOT as simple as clear as possible since "done" doesn't mean "done" even though it is labeled as "done."
Actually, it's not contradictory, it's your choice of status names and/or column configuration that make the conflict. If you use the default settings in Jira, it will put done in the done column and hence there's no conflict.
I have used the following to help indentify an issue's finished state:
Workflow Status of Done ✔️
Resolution field value to indicate how it entered Done.
Done, Rejected, Can't Reproduce etc...
Instead of automatically setting the Resolution to Done when an issue is dragged to the Done column, force a screen the allows you to indicate how it got done. Required field of Resolution
Keep all Workflow "end" steps in the right column which is required for sprint close out.
Use a Jira dashboard for reporting the types of doneness. 😀
Agile boards are not intended for reporting, they are intended for a team to move planned issue's through the flow.
I am trying to understand the problem that you are trying to solve, but based off the information provided, I believe you want to setup some transitions on your workflow. This will allow you to have one Done status (and one thus one Done column) but still track outcome.
If that is correct here is a mock scenario that shows you how to do that and the result:
🙂
It looks like you're new here. Sign in or register to get started.
