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

Closed issues being suggested to move to new sprint when completing a sprint

Esther Strom

A user reported this issue to me.

Their team has a sprint board with a number of tickets. All of the tickets are closed, but when they try to mark the sprint as complete, Jira is asking to move all of the tickets to either a new sprint or the backlog.

(In the screenshot, this is a board that was created using a filter that pulls in two projects. There is a sprint that contains two tickets from each project; all of the tickets are closed with Resolution = Done. The four visible tickets in the Done column are the only tickets in the sprint.)

Any idea why Jira thinks there are open tickets that need to be moved to a new sprint?

Accepted answers

Nic Brough -Adaptavist-

This suggests there are a number of hidden issues - the board should be showing 24 issues, not just 4. I suspect the 4 on the board are not the 4 that are going to be carried over.

Could you do a search for "sprint = <name of sprint>" in the issue navigator and see what issues that returns, and check their status and resolutions?

All comments

Nic Brough -Adaptavist-

This suggests there are a number of hidden issues - the board should be showing 24 issues, not just 4. I suspect the 4 on the board are not the 4 that are going to be carried over.

Could you do a search for "sprint = <name of sprint>" in the issue navigator and see what issues that returns, and check their status and resolutions?

Esther Strom

Thank you; that was it. My user did not indicate that there were other projects using that sprint that were not displaying on their board.

Wait, nope. I mean yes, there are other issues that display when I search for the sprint name. But that filter returns 7 tickets that are not Closed; why would only 4 be suggested to be moved to a new sprint/backlog?

Nic Brough -Adaptavist-

I think it's based on what column the issue would be in if it were on the board.

What are the status and type of the 7 unclosed issues?

Esther Strom

One task, four stories, two defects. The task is In Progress, the stories and defects are a mix of QA Untested, Staging Untested, and Production Untested. There are not four tickets in a single status that would account for the four it's trying to move.

Without actually clicking to complete the sprint and see which four of the seven Jira thinks should be moved, I don't know how it's deciding.

ETA this is how the columns/statuses are mapped. So in theory, the three tickets that are in Prod Untested are considered Done, so it would be the remaining four that might be moved? OK, that sort of makes sense.

Chris Green_253rbq

I have a similar issue @Esther Strom

Each time we close a sprint (~monthly) there are additional issues that are rolled over to the new sprint

Within each sprint, we do a number of releases and 'releasing' the tickets in JIRA sets the status of the tickets in that release (aka fix version) to 'Closed'

Only 1 sprint is active at any time, and the 'Active sprints' Board, currently containing 90 tickets of type Bug, Task, Epic, Spike, Improvement, New Feature (no sub-tasks), in status'
Reopened, In Progress, Under Review, Ready for QA (No 'Done' or 'Closed' tickets)

The 'Backlog' view contains 1 active sprint and 2 inactive (future) sprints and a Backlog

On the 'Column Management' page (RapidBoard.jspa?rapidView=12&config=columns) there are 2779 issues showing as 'Done'

When trying to close the sprint it shows "0 issues were done" (consistent with the above) but then shows "511 issues were incomplete"

When I search issues by Sprint 520 issues appear, 429 of which imported in to the sprint from the last sprint as "Closed" (with varying resolutions, Duplicate, Won't Do, Done, Not Applicable, etc) from as far back as June 2016 that have been rolled through 17 different sprints

This affects the burndown chart, as the story points are not shown as released at the end of any sprints

I tried doing a bulk action to Close all tickets, but they still rolled over to the next sprint

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

sprint