Can there be multiple "Closed" statuses in a Jira workflow?

[Martin Härri]

We have the situation in one of my projects that we do not always release at the end of a sprint, or increment, but put the code goes to a "waiting" status, and later we release the outcome of multiple sprints in one go. For that we have added a status "Ready for Release" in the workflow. However, we are realizing that story points are only counted when the issue is in status "Closed", which might be several sprints later than when the work was actually done. That makes all velocity, burnup etc reports from Jira useless, and we have to work with an Excel report with quite complicated formulas.

Now my question is: can i have several statuses which are considered "Closed", or can I set an issue to "Closed" and set a flag or something indicating that the issue is not released yet, and then remove that flag later?

[Fabio Racobaldo _Catworkx_ · Accepted solution]

Hi @Martin Härri ,

all statuses that you consider as closing status for your sprint should be placed in the last column of your scrum board.

For example, if you have Resolved and Closed considered as closed statuses, and a ticket has been moved to Resolved  that means that team completed work on that ticket (burndown chart should correctly decrease story points) but, in order to be moved from Resolved to Closed (releasing) you need to perform a new transition on the ticket itself.

Hope this helps,

Fabio

[Martin Härri]

Hi Fabio

Thanks a lot, I can confirm that this is true. I have compared the metrics of 2 teams, one has "Ready for Release" in the last column (together with "Closed"), and story points are counted, and the other team has that status in the second to last column, and sp are not counted. Brilliant!

[Rilwan Ahmed]

You can have multiple "Close" status in a workflow and can be done in many ways. 

1. In the existing workflow, add new transition (using diagram mode) by option Re-use transition available. Select from status and to should be "Closed". This will have same conditions, postfunctions, validators from existing trnasition. 

2. For the existing close status, create new transition from required status. You can create same from any status.