Incomplete items are moving to backlog instead of next sprint while closing the sprint

shashi sharma
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!
January 22, 2023

When i close the sprint and move all incomplete items to next sprint, few of the incomplete items are moving to backlog. Can anyone help me explain why this is happening? My board configurations are correct. What is the criteria to move incomplete items to next sprint apart from its status?

5 answers

2 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 22, 2023

Hi @shashi sharma and welcome to the Community!

When you close a sprint, Jira normally asks you what should happen with the incomplete issues. If you select the option "move to next sprint", Jira should automatically do that for you.

Moving an issue to a sprint does not have anything to do with status. The only thing that happens, is that Jira adds the reference to the next sprint to the Sprint custom field on your issue. Basically, it just updates a value on your issues.

The problem you experience has possibly some relation with what you expect that would happen (and something else does). A couple of things to consider:

  • incomplete issues are all the issues that did not reach the rightmost column of your board when you complete the active sprint;
  • in order to move issues into the next sprint, you must have created one already in the backlog of your scrum board before you close the current sprint. Jira does not do that automatically for you;

Maybe there's an explanation in one of those suggestions already. If not, you would need to be more specific about what you do exactly when you close a sprint, what your configuration looks like and what your expectations are like. That may provide additional clues as to what may be going wrong.

Hope this helps! 

0 votes
philipf
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 Leaders.
May 21, 2024

It seems like we are going in circles here, and not addressing the issue.


Issues that are not done, are being put in to the backlog, when should be moved to the next sprint.

This has nothing to do with columsn and what they are in. We are all advanced users and that isn't it.

Please explain why some tickets get moved that are not done in the status or the underlying status?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 23, 2024

When you close a sprint containing issues that are not done (i.e. in the last column), Jira asks you if you want to put the issues into the next sprint or the backlog.

So, the answer to "why" is that your people are clicking on "put open issues back in the backlog"

0 votes
Michal H April 12, 2023

Hey @Walter Buggenhout @shashi sharma @Nic Brough -Adaptavist- 

We face similar issue. I explained that more exactly answering the post from Nic in the topic created by me, you can find below. It looks it is exactly the same bug as shashi describes here
https://community.atlassian.com/t5/Jira-Software-questions/A-bug-when-closing-a-sprint-and-moving-not-done-items-to/qaq-p/2328728 

0 votes
Michal H April 11, 2023

We face similar bug. When we close the sprint, we select the next sprint from the list (eg. we close 'sprint35' and we select 'sprint36') where all not done items should be moved. We observe that some of not finished items are moved to that sprint (sprint36), some of them not. Any idea what could be the reason?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 11, 2023

You'll find that the issues that move to the next spring are not "done", or have sub-tasks that are not "done".  That means "in the last column on the board" (and it applies to all sub-tasks - you need to have them on the board)

Michal H April 12, 2023

Hey @Nic Brough -Adaptavist- 

I pasted a link to the topic above, where I explained that better I believe we are not on the same page, thanks for the input 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 12, 2023

I think we are, you are asking why issues do or do not move to a new sprint when you close the current one.  The answer is as @Walter Buggenhout have said - look at the column the issues are in when you close the sprint.

0 votes
shashi sharma
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!
January 22, 2023

Thanks @Walter Buggenhout  i follow the procedure to move items to next sprint but some “incompleted issues” are moving to backlog. I have already checked the status mapping of my board and that is rightly done. The only difference i can see is in the components used. These components have been configured in filter query of my board. I am not sure if that is the reason.

Still I could not figure out the possible reason for this issue?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 12, 2023

The issues that do not move are not in the last column on the board and/or have sub-tasks that are not in the last column.

Suggest an answer

Log in or Sign up to answer