One issue with multiple sprints

When we cannot finish the backlog in the current sprint, we would like to add it to the next sprint's backlog, right now if the issue is partially done with comments etc, we will need to clone the issue to the new sprint in order to avoid affecting the burndown chart, but this will lose the existing comments and logs unless I link it to the existing one, which is not very ideal.

1 answer

Hi James,

When you end a sprint, any incomplete or partially completed issues are moved to the next planned sprint. If you do not have a planned sprint, it is moved back to the backlog. There is no need to clone the issue again.

Hi Bhushan, when you move tickets to a newer sprint, it affects the burndown chart for the old sprint.

Dan Radigan Atlassian Team Feb 09, 2015

James- Velocity is the number of story points the team can fully complete in one iteration. When the sprint ends and stories aren't complete, the stories should not be counted in the team's velocity for that sprint. They should move to the backlog or the next iteration based on the product owner's direction. When the team completes that story in the next iteration, they get the full story point value in that iteration. One thing to look at is the team's definition of done which we talk about in sprint review: Also, if tasks are too large and frequently moving between sprints, it may be helpful to go to a further level of granularity in sprint planning. Having finer grained work will help make velocity more consistent.

Related problem:
It appears that JIRA adds multiple sprints to an issue when it rolls over from sprint to sprint. For example if an issue could not be completed in Sprint 1 and is rolled over into Sprint 2, then JIRA adds Sprint 2 to the "Sprint" field of the issue while also retaining Sprint 1 in the Sprints field. If the issue again rolls over to Sprint 3, then JIRA also adds Sprint 3 as well to the "Sprint" field of the issue, so now the Sprint has 3 values. 

Implication: The same issue appears in Sprint Closure Reports for all the three sprints which is not correct and this messes up reporting.

Question: What is the "right" way to rollover issues so they do not appear in multiple sprints (drag & drop, close sprint) 

We also have this issue, especially where issues cross projects and people don't have permissions to both projects. It gets very messy.

Whether the issues are moved to another existing or New Sprint the Sprint it was moved from, remains in the Sprint field. Even if you move it to the Backlog at the end of the sprint, it still leaves the previous Sprint name in the Sprint field, even when it sits in the Backlog.

Am I doing something wrong here? Using JIRA wrong? Understanding agile wrong? HELP!!!

You are doing nothing wrong. Unfortunately, it appears that Atlassian does not offer any way to get this visibility via queries.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,805 views 18 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you