Customized "Done" status not being closed after sprint competed

[Simon Wong _Goldhorse_]

Hi,

New to Jira, hoping someone can help me.

To better track where each development requests are, I have customized some workflow status.  One of those is "In Production" status which indicate that the Jira ticket is in production.  It is created under the "Done" category.  We market these Jira tickets to "In Production" after a release is executed.

What I have noticed is that when I completed a sprint, these "In Production" Jira tickets is assumed to be still open and get transferred to the next sprint, which is not correct.

Now, I am trying to do two things:

1) Associate these "In Production" Jira tickets back to the right sprint and 

2) Configure the system so that these "In Production" Jira tickets can be closed when I complete a sprint.

Can someone help me?

Thanks,

Simon

[Matteo Vecchiato]

Hi @Simon Wong _Goldhorse_ ,

Thank you for your post.

Is the status "In production" mapped to the last column in your board? As explained in the following article the work items are considered closed if its status is mapped in the last column of board: 

https://support.atlassian.com/jira/kb/done-or-resolved-work-items-are-shown-as-incomplete-when-closing-sprints/ 

Hope it helps.

Regards

[Tomislav Tobijas]

Hey @Simon Wong _Goldhorse_ ,

To quote official article:

When you complete a sprint in Jira, the only work items that Jira considers completed are work items set to a status that is mapped to the rightmost column of your Jira board.

Meaning, you'll have to play a bit with board columns and place that "In production" status to the rightmost column.

There are a couple of feature requests related to this:

• JRACLOUD-94122: When working with sprints, we want Jira to consider the statuses are done, and not the column order (right-most column) 
• JRACLOUD-90410: Update Report Logic where 'Done' is based on a status category or workflow 

💡 One more tip would be to use "Resolution" field when reaching those green statuses as Jira actually considers something as Done only when the item has a Resolution value set.
More on that here: Best practices on using the "Resolution" field in Jira Cloud 

You could, for example, use workflow rules (ex post functions) to set or remove Resolution field value on transition.

Hope this helps.

Cheers,
Tobi