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

Sprint disappears from board when all issues are removed

Brennon Bortz

I know there are better ways to do this, but we have a "bug triage" sprint that we use as a bucket for all new defects. As QA/testing finds things, they assign them to this sprint. As defects are triaged, they have necessary fields populated, etc., and are then placed/prioritized in the backlog.

This sprint has been "emptied" of issues many times (that's the target state, after all). For some reason, though, now when it's emptied, it no longer shows on the board. If I create a new issue, assign it to that sprint, and refresh the board, the sprint appears and shows that one issue. If I delete that issue or assign that issue a different sprint and refresh the board, the sprint disappears again. Any idea what might be happening here?

Accepted answers

All comments

Pete Singleton

The board will only show Active sprints. It sounds like the Sprint has previously been closed, and so by emptying it of issues it will disappear. But by adding issues again to it, it will become Active again.

If you add an issue to it, you should be able to see the Start/End dates of the Sprint. If the end date is in the past, then it has been previously closed. Just move the end date out to the future and it should work as it did before.

Pete Singleton

Actually I'm not sure this will work, as when the sprint is empty again it is considered closed again.

You could create a new sprint, with the same name if necessary.

Brennon Bortz

Actually, I don't think the sprint was closed. When I get it to show up on the board, there are no dates, and I have the option to start the sprint.

Pete Singleton

How does the sprint look on the Sprint Report when it's empty?

Pete Singleton

There's another way you could do this... if you create an Epic for "Defects to Triage" and assign all new defects to that Epic. Then on the Scrum board you can filter your backlog based on the Epic (using the Epics panel on the left hand side). As you triage, you reassign to the correct Epic (or remove the Epic altogether if necessary).

Brennon Bortz

Yep, that's a completely valid approach. I'm really interested in what's happening with this weird sprint, though.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-core

jira-core-server