Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do you close a sprint when error message "Failed to complete Sprint"?

Jaydra von Behren
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 12, 2025

Multiple teams within my company are not able to close a Sprint. 

We are getting the error message: 

Failed to complete Sprint - This issue cannot be edited because of its workflow status. 

 

Can you please help us trouble shoot this issue? Our SOPs have not changed but multiple teams are experiencing this for various Sprints.

5 answers

5 votes
Chris Rogers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
December 12, 2025

Hi @Jaydra von Behren

It sounds like there might be something in the workflow that has changed and one of the issues that's in the sprint can't be updated correctly.  If Jira provides you with the specific issue key, can you please check the status it's in and if you have access, check that status in the workflow?

Sometimes statuses (usually closed/resolved) can be configured so they don't allow edits while in that status (see workflow properties)

2 votes
John Funk
Community Champion
December 13, 2025

Hi Jaydra - Welcome to the Atlassian Community!

Make sure that your final status is mapped to the last column in the board. Only work items in the last column of the board (regardless of status) are considered Complete. 

If that is not the problem, check the workflow to be sure there are no rules on the transition to the final status that would prevent issues/work items from being moved there. 

John Funk
Community Champion
December 15, 2025

Are there sub-tasks for any of the tasks in the sprint that are not completed? You might do a filter to show all work items in the Sprint to check the status of all work items. 

Sprint = Sprint 74 (or whatever the actual name is. 

0 votes
Swathi Acharya
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 15, 2025

Hello @Jaydra von Behren

Welcome to Atlassian Community!

This error usually occurs when the workflow has a status which has the property "jira.issue.editable=false" set.

Setting this workflow property prevents editing the issue. Moving an issue to a different sprint is in fact editing that issue and changing the value of the field Sprint.

To fix this, you can modify the workflow to remove the property and then publish the workflow to successfully complete the sprint.

I hope that helps!

Thank you

0 votes
Jaydra von Behren
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 14, 2025

Hi @Duc Thang TRAN @Chris Rogers @John Funk 

Thanks for the input. We are in Sprint 76 now.

Sprint 74 - cannot be closed.

All work items are complete (User Stories = Closed, Tasks = Done)

Sprint 75 - cannot be closed. 
Work items are in a variety of statuses: 2 not started, 13 in progress, 83 completed. 

All tickets in both Sprints have a status in the column.

Is there a way to get an Atlassian member to check out our workspace and assess what is going on specifically?

Chris Rogers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
December 15, 2025

Hi @Jaydra von Behren 

If you'd like Atlassian to check something for you, you'd need to open up a support ticket at https://support.atlassian.com

Are you able to check how the workflow is configured to see if it allows you to edit closed/resolved issues?

0 votes
Duc Thang TRAN
Contributor
December 14, 2025

Hello @Jaydra von Behren 

This is a combined answer from @John Funk  and @Chris Rogers 
Chris explains why you can’t move an item from a closed sprint to another sprint (because editing issue properties is not possible ).
John explain the common user case is that final statuses are not in the last column on the right, which can skew sprint reports.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events