Ways around the last column being the only one to be considered done in a sprint?

[Hannah Bauhof]

After reading this community question: https://community.atlassian.com/t5/Jira-Core-questions/Sprint-completion-on-two-columns/qaq-p/1094102

Our team figured out why our sprint charts - burnup and burndown - didn't look accurate for the work we had been considering as 'done.  We had 4 status that we consider "done" but we put those in 2 columns or had them 'off' the board. 

• In develop branch - Done - second to last column
• Archive - Done - off the board
• Staging - Done - last column
• Pending Release - Done - last column

Now that i know that Jira only considers one/last column to be done, is there a way around this last column limitation? 

If not, what's the point in setting status resolutions being "done" if the real "done" is only tracked by the last column for sprints?

---

Also, this would have saved us lots of time if there was a note somewhere in the board settings stating this limitation. Maybe there is but i missed it? Maybe I should have figured this out more easily and maybe we just have our sprint board set up in abnormal ways? 

[Jack Brickey · Accepted solution]

Hi Hannah, that is correct. The last column in what drives the sprint closure and kanban release actions. The only way around it would be to collapse all of your done category statuses into the RH-most column. Then when the user drags/drops an issue to the 'complete' column they would see several 'drop-boxes' to place the issues into.

FWIW, this is an often misunderstood fact for folks just starting out as can be seen by the many posts on this in the Community.

[Hannah Bauhof]

Thank you, sounds like something that should be made more clear in the board settings. 

[Dharmesh Barot]

We are running into the same issue where our workflow is somewhat like

Backlog > Define > Development > QA > Ready For Prod > Prod Deploy > Done

Most of our sprints have tickets in Ready For Prod. Since we don't deploy to prod tickets sit in that column and reports show tickets weren't closed and work was not done.

Done marks the ticket as resolved in the workflow.

Is the solution then to have 2 boards?

Development Board

Backlog > Define > Development > QA > Ready For Prod

Prod Board

Ready For Prod > Prod Deploy > Done

How will the tickets be resolved with two boards?

Will the reporting reflect accurately since reports are based on boards?

Please advise.

[japneet_kaur]

Hi @Dharmesh Barot
I'm in a similar situation as what you described. What did you finally end up doing in this scenario?

[Jack Brickey]

Two boards is the path I have chosen in the past when face with similar scenario.

[Dharmesh Barot]

@japneet_kaur We did the same thing as @Jack Brickey