Issue-loaded Sprint does not recognize issues when starting the sprint

[Ronny Dorian]

I drag issues into the sprint section at the top of a backlog and when I click on Start sprint, it will tell me that only 1 issue will be in the sprint or even 0 in some cases. I only have this issue with one Jira company-managed Scrum project.

As you can see in my screenshot, I have 4 issues loaded but it says "1 issue will be included in this sprint"

I anticipate that part of the problem here is that the Jira Issue(s) was associated with a prior sprint in which it remained in the to-do or in progress, and when asked to carry over to the next sprint I clicked yes (most likely). When I click into the Issue now, I see that it is not part of any sprint but was in another sprint, which I think is getting in the way for some reason.

Lastly, I get the same problem in this project for both a currently running sprint or a new one being planned that has not started.

Any ideas? If necessary, how can I possibly remove the previous sprint association from these Jira Issues?

Thanks, Ronny

[Trudy Claspill]

Hello @Ronny Dorian 

Welcome to the community.

I'm not really sure what is causing your problem, but the fact that an issue was in a previous sprint is unlikely to be the cause. Jira is designed so that the history of the sprints to which an issue was assigned can be retained in the issue. If you remove the historic sprint references, that will change the reports for what happened in those historic sprints with regard to that issue having been part of that sprint and not completed during that sprint.

In the example image you showed above where it shows 4 issues in the sprint in the background but the pop-up says only 1 will be included, what happens when you do start the sprint? Does it push the other three issue back into the backlog?

You said you have "the same" problem with a currently running sprint. Since a currently running sprint can't be "started" again, can you provide more information about the steps you are taking with a currently running sprint and the responses you see indicating a problem.

[Ronny Dorian]

Trudy, thanks for your reply.

Yes, when you start the sprint, it pushes the 3 other issues into the backlog.

With regards to a currently running sprint, if I drag an issue up to it, it will tell me scope will be impacted, and I accept that. However, the issue will not stick to the sprint - it will fall back into the backlog. I hope that explains it more.