nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

One issue with multiple sprints

James Lin

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.

Accepted answers

All comments

Bhushan Nagaraj_ae5psb

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.

https://confluence.atlassian.com/display/AGILE/Ending+a+Sprint

James Lin

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

dRad

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: http://blogs.atlassian.com/2015/02/sprint-review-atlassian/. 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.

Rahul Sawhney

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)

Rafael Longo

I'm having some problems with the Sprint field.

In the field, there is only the last sprint where the story is or was and not all the accumulated sprints that this story has been worked for.

Can someone help me?

LoriAnne Carpenter

I have nothing to offer, but you're not the only one. Some of my issues seem to retain all of the sprints, while others do not

David Johnson_nhp39g

Same here. An Issue with Type being task that is moved from one sprint to another retains the prior sprint information. Let's suppose that you have a Task that was in "Sprint 1", then got moved to "Sprint 2". When you run a filter, the column shows both Sprint names in the field on the screen, separated by a comma. What is interesting is that exporting the filter to a CSV file shows there are *two* columns, each with the identical Column Header name being "Sprint." In the first column, the Sprint is "Sprint 1"; in the second column the Sprint is "Sprint 2."

Guess what? Suppose the Task subsequently moves to "Sprint 3." Now all 3 sprint names show up for the task, and there is *third* column in the CSV file! Looks like this just continues and maybe this is a JIRA database constraint?

Please help. Having a Task showing up in multiple sprints throws off our dashboards and statistics.

Steven Derwent_aq9mg6

I'm seeing a similar issue as well with cloned tasks inheriting the sprint value on the new task. I cannot remove the value from the new task, so it looks like it was not completed in the other sprint. To make it more confusing, the new task does not appear in the older Sprint report. Very odd behavior (Jira server 7.13.5).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud