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; } } }

Issues Not Rolling Over in Sprint

Lauren Folley_6sfd7t

I recently found that only some of the Issues on my board are making it to the next Sprint while other are put in the Backlog.

We have one Project that houses several Boards/Epics. The board where I complete/start Sprints houses a query where all epics associated with my App team and my Reporting team are put together.

When I complete the Sprint, I choose to move the open Issues to the next Sprint I have coming up (yet to start). Only the Issues from my App Team's Epics make it into the Sprint. The Reporting Team's Issues all go to the backlog.

Trying to determine if I am doing something wrong or if something has changed? How do I get ALL Open/Unresolved/In Progress Issues in my current Sprint to roll over to my next upcoming Sprint?

Accepted answers

All comments

Radek Dostál

Well, let's start by calling it "issues" and not "Jira's" because that gets confusing real fast.

When you are closing a sprint - it will consider issue to be completed only if that issue is resolved (= has 'resolution' value), and if that issue is in the right-most column. Likely, when you are closing the sprint, some of the issues are resolved and in the right-most column -- thus they are completed and seen as done -- whereas other issues are either unresolved or not in the right-most column -- thus they are seen as incomplete, and are moved over to the next sprint.

I don't however really understand the intent here, because it sounds that you want to move all of the issues to the next sprint. Why? They should be ideally worked on and closed in the sprint. You don't want to have "work leftover" and have to catch up with it in the next sprint. You estimate your sprint's workload, and try to finish it in the sprint's timeframe, close the sprint - move on to the next sprint.

(And if some issues do not get completed in time - then they are moved over and worked on in the next sprint. But what I'm confused with is when you say you want to move all issues to the next sprint.)

Lauren Folley_6sfd7t

The issues that are not rolling over are not completed and are not in the right most column.

The intent here is that this is how our workflow works - not all work gets completed and so whatever is not completed gets rolled over. I'm not really looking for help here.

I have a board that pulls in multiple Epics and only issues in SOME of my Epics are rolling over. The epics are exactly the same the issues are formatted the same. The only difference is a handful are for my App team and a handful are for my Reporting team.

Nic Brough -Adaptavist-

Hmm, can you tell us some more about the config of your board and some of the data? I'd like to see

The query for the scrum board
What status are in the last column
An issue that did move to the next sprint (just the standard system fields in Jira - issue type, status, resolution, and epic link etc. Don't need the content of summary, description etc)
An issue that went back to the backlog (same fields)
The workflows for the two issues, if they're different, or the shared one.

Lauren Folley_6sfd7t

Query: project = ORION AND (("Epic Link" = EMPTY AND component in ("Sales Credit", "Sales Compensation", ASP, SP, "Sales Compensation Reporting") AND updated >= -720d) OR "Epic Link" in (ORION-11921, ORION-39873, ORION-39978, ORION-39979, ORION-39980, ORION-39981, ORION-41250, ORION-36257, ORION-41474, ORION-52441, ORION-53783, ORION-17315, ORION-40776, ORION-40778, ORION-41785, ORION-55282, ORION-55283) OR (assignee in (joberg, melpet, hoking, sasdqr, dyclay, mahfre, keglov, sayada, risylv, kimorg, trsong, sasull) AND updated >= -180d)) AND (assignee not in (chrwil, cancss, sassft) OR assignee is EMPTY) ORDER BY Rank ASC, key ASC, created DESC

Done: Closed

Issue that Moved: Type=Story, Status=To Do, Resolution=Unresolved, Epic=ORION-55283, Component = Sales Compensation

Issue that Didn't: Type=Story, Status=In Progress, Resolution=Unresolved, Epic=ORION-55282, Component = Sales Compensation Reporting

Workflow: Shared by all Issues in Project

Screen Shot 2022-03-14 at 2.39.13 PM.png

Nic Brough -Adaptavist-

Wow, thank you! I wish everyone responded with information like that when asked for more data!

The bad news is that you've completely ruled out all the things I was thinking it might be. The only thing left is a question about the dates you've got in the query - is it possible that the issues that are not moving into the next sprint have gone past the "updated in the last X days" line? (I completely expect it to not to, but I have to ask)

The other question which I didn't ask before and should have - do either of those issues have sub-tasks? If they do, then what status are those sub-tasks in?

Lauren Folley_6sfd7t

The Issues were updated/created at minimum 2 weeks prior to this sprint change so I don't think that would have caused them.

Both Stories had subtasks that were To Do at the time of rolling over.

The only true difference I can find is that the Issues are in different Epics, but this had never been a problem before. When I changed how we were rolling over the Sprint from moving the issues manually to using the built in Sprint Rollover system, this was working. Around January 25th is when my Sprint Rollovers stopped capturing the Issues in the second Epic.

Krzysztof Karski_gi6rhs

We are facing the same issue on our JIRA Cloud project and it started happening in March. Before then, it worked as expected.

As of March, when I close an active sprint and select the next sprint to roll over into (not yet opened), the completed stories are eliminated but the still open issues all go into backlog and various teams have to re-add them to the new active sprint manually.

Adriana Pennacchioli

We are also facing the same problem. Has anyone been able to figure out if this is a bug that Atlassian has been notified about or if there is some type of solution for this issue?

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server