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

Backlog items shouldn't be shown in the active sprint but in the sprint backlog

Anja Eigner

Hi there,

a product owner wants to have the status "backlog" not shown in the active sprint board but in the backlog section. Means she has 35 tickets planned for the sprint and only the ones with the status "ready for development" or further should be shown on the active sprint board. However, as soon as she moves to the backlog section, she wants to see the tickets from the active sprint + the tickets with the status "backlog" which are assigned to the active sprint.

Any ideas?

Thanks & best,

Anja

Accepted answers

Trudy P Claspill

Hello @Anja Eigner

I assume that in your scenario "Backlog" is an issue Status.

The design of the Scrum boards in Jira is such that an issue can be in any Status while assigned to a Sprint. The issue will show in that Sprint regardless of the issue's Status.

You can't remove the "Backlog" Status/Column from the Active Sprints board view. If you do that, then the issues in the "Backlog" status will no longer display in either the board view or the Backlog view.

Your options are:

1. Create a filter on the board that the PM can activate to hide issues that are in the "Backlog" status.

2. Create an Automation Rule that will automatically change the status of issues in a sprint from Backlog to Ready For Development when the Sprint is started. The Backlog column would remain in the Board view but be empty unless somebody intentionally moved and issue back to that status.

Laurie Sciutti

Hi @Anja Eigner ~ I'm not sure you can do that natively, but you could create a quick filter (Status != "Backlog") on your board so that when selected, those items are filtered out. Curious if anyone else has suggestions...

All comments

Trudy P Claspill

Hello @Anja Eigner

I assume that in your scenario "Backlog" is an issue Status.

The design of the Scrum boards in Jira is such that an issue can be in any Status while assigned to a Sprint. The issue will show in that Sprint regardless of the issue's Status.

Your options are:

1. Create a filter on the board that the PM can activate to hide issues that are in the "Backlog" status.

Laurie Sciutti

Anja Eigner

Hi @Trudy P Claspill ,

thanks for your feedback.

It's not exactly what I was looking for but sounds like there is no other solution for the PM's problem.

Best,

Anja

Anja Eigner

Thanks anyway @Laurie Sciutti

Trudy P Claspill

Hello Anja,

Is this for a Company Managed project or a Team Managed project?

If for a Company Managed project another alternative would be to create another Board and there have the Backlog status not mapped to a column. That would prevent all issues in that status from being displayed, but would enable the PM to have a board where issues in that status are not displayed and no column is shown.

However, it would not prevent issues in a sprint from being put into the Backlog Status. If that occurred the issue would disappear from the board.

Again, you could use Automation Rules to automatically transition issues out of the Backlog status when a sprint is started. And it might be possible to create a workflow condition that would disallow transitioning an issue in an Active Sprint back to the Backlog status. Or possibly you could create an Automation Rule that would remove the issue from an Active Sprint if it was transitioned back to the Backlog status.

There are various "workarounds" for this, but none are a perfect match for what you PM wants as that does not align with how Jira Scrum Boards actually work.

Anja Eigner

Thanks @Trudy P Claspill !

It's a Company Managed project. I will let the PM know and let' see how we will solve this.

Thanks again.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

sprint

backlog