I had one request from user and it's related to Jira Software (Company Managed).

[Suria Kirtnhi Chandran -]

[Hi Team,

Currently, when we close a sprint, all tickets are required to be marked as “Done”, and any tickets not in the “Done” status are automatically carried forward to the next sprint.

Going forward, we would like to modify this behavior. We should be able to close a sprint when tickets are in either “Awaiting Deployment (AWD)” or “Done” status. Only tickets that are not in AWD or Done should be moved to the next sprint.

Implementing this change will help us manage spillover tickets more effectively and improve sprint closure accuracy.

Could you please help in configuring this behavior?

Thanks for your support.]

I'm not sure how to assist on this

[Jack Brickey · Accepted solution]

Hi @Suria Kirtnhi Chandran - , if you place the AWD status in the right-most column along with Done issue then this would achieve your goal. Jira only considers issues in the right-most column to be complete. Any issues in any other column on the board, when the sprint is marked as complete, will be moved to the next sprint or the backlog depending on your selection.

[Suria Kirtnhi Chandran -]

I've already made this changes but still user say can't reached the expectation

[Staffan Redelius]

Hi @Suria Kirtnhi Chandran - 

As @Jack Brickey describes, Jira only treat work items in the right-most column as finalized when closing the sprint. The color of the status, the name of the status or if there is a resolution set does not affect the sprint burndown, sprint report or carry-over to the next sprint.

It doesn't work retroactively meaning already closed sprints will not be affected. You can open up closed sprints via the sprint report and close it again with your new configuration but be aware that it will mess up your reporting when it comes to velocity etc.

Could you provide a screenshot or a more detailed description of what isn't working as expected?

Best regards,
/Staffan

[Jack Brickey]

Hi @Staffan Redelius , this is not accurate. The status category does not influence what is considered complete in a sprint. The only thing that is required is for the work item to be in the right most column. However if the work item has subtasks that are not in the right most column then it will not be considered complete. @Suria Kirtnhi Chandran - , is it possible that your awaiting for development work item has some tasks that are not complete?

[Staffan Redelius]

Hi @Jack Brickey Where do I say that Status Category influences what is considered complete in the sprint? I say the exactly the oposite, only issues in the right-most column will be considered done in the sprint regardless what the status is called or what color it has. 

Jira won't let you close the sprint if there are open sub-tasks even if the Parent is in the right-most column,

[Jack Brickey]

@Staffan Redelius , DOH! I meant that comment for @Polina-DevAcrobats- . I clicked on the wrong user in the auto-complete. Sorry for the incorrect callout.   :-(

[Polina-DevAcrobats-]

@Jack Brickey, you’re absolutely right. Thanks for explaining!

[John Funk]

@Staffan Redelius  - you have to forgive @Jack Brickey as he is old and senile sometimes. 

[Jack Brickey]

😂 well that is so true! I made myself a post-it note to slow down and be more careful but I forgot where I put it. 🫤

[John Funk]

Haha - I have to do the same. 

[Polina-DevAcrobats- · Accepted solution]

Hi @Suria Kirtnhi Chandran -

I’d like to jump in with a quick suggestion. Based on the screenshot you shared, it looks like you’ve mapped the “Awaiting for Deployment” status to the Done column, as advised. However, the status is still highlighted in blue, which indicates that its status category is set to “In Progress,” not “Done”.

If you update the status category for this status to Done, it will appear in green and be treated as a completed status by Jira.

Hope this helps!

Regards,

Polina

[Suria Kirtnhi Chandran -]

But the "Awaiting for deployment" status is share by 20+ project and also any edits would affect those other projects as well.

[Suria Kirtnhi Chandran -]

Thank you all for your support.