Remove Incompleted Issues In Completed Sprint

[Joe Taberna]

I have issues that are not done and do not roll over to the next sprint. I want to move them into the active sprint so I search for the issue, perform a bulk change changing the sprint field using the sprint number of the active sprint. Doing this does change the sprint, but it does not appear in the active sprint board or backlog.

Is there a fix for this?

How can I make sure incomplete issues roll over to the next sprint? 

[Petter Gonçalves]

Hello Joe,

I hope you are having a nice start of week.

The default behavior of JIRA when you close your Sprint is to pop-up a message asking if you would like to move the incompleted issues to the next Sprint or to the backlog of your board. 

Can you please let me know where the incompleted issues remain when you close a Sprint? Are they moving to the backlog of your board or just remaining in the completed Sprint?

Also, are you using JIRA Classic projects or Next-gen?

Here are some possible reasons for the problem:

- The incomplete issues are configured with a valid resolution, so they would be considered resolved

- The incomplete issues are configured with the status that is in the last column of the board

- There is no Sprint planned after the closure of the current Sprint, so the incomplete issues will be moved to the backlog.

Here is a good article about this Sprint behavior on JIRA:

- Carrying forward unfinished work in Sprints

Let me know if this information helps.

[Joe Taberna]

Petterson,

Thanks for the response.

-We are using classic projects.

-There's no resolution.

-The status in the last column of the board is "Done" and not the "Ready For QA" the tickets are in.

-There are planned sprints that we can roll the tasks over to, but they don't and even if there is not a sprint they do not appear on the backlog.

The only thing I can think of is if the ticket was marked done, but then reopened after. Would it still have a resolution date or would that disappear when the status is changed?

[Petter Gonçalves]

Hello Joe,

Thank you for your answer.

If you are clearing the resolution field with a post function when the issue is reopened, so the problem should not be happening at all. That's the correct way to clear the resolution field when an issue is reopened.

Another possibility that could cause this problem is that someone has created a valid resolution called "Unresolved" to manually populate the issue when it is reopened. This is not a correct workaround and will cause your issues to keep appearing as resolved in the system.

Perform the steps below to check if you are facing this scenario:

Navigate to your issue navigator and search with the following filter, setting the issuekey with the issues that remained in the Sprint after its closure:

Resolution is EMPTY and issuekey = ABC-123

If the issues of your Sprint are not returning, your issues are configured with a valid resolution and you would need to bulk clear it. 

Please, check the detailed documentation below to know how you can create the post function to clear the resolution and how you can perform the bulk operation to apply it in your issues:

How to Bulk Clear Resolution

Let me know if this information helps.

[Petter Gonçalves]

Hello Joe,

Have you had the chance to verify my last answer? Has it helped you?

[Joe Taberna]

I figured it out. The board I was looking at was for issues assigned to a specific assignee and not everyone.

[Tomaz Alexandre Macedo Rodrigues]

There are two ways:

Usually I put it in "Done" and make a copy, using "Splite issue" (this is in the other Sprint).

But there is another way (which I say is unregular because it breaks the burndown) that would just move it to the next Sprint ...

[Tomaz Alexandre Macedo Rodrigues]

There are two ways:

Usually I put it in "Done" and make a copy, using "Splite issue" (this is in the other Sprint).

But there is another way (which I say is unregular because it breaks the burndown) that would just move it to the next Sprint ...