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 - issues not visibles

LAMBERT Emilie

Hello,
We are using a jira software project and a new Scrum Board (created since we decided to stop working with kanban method).
I noticed that issues in the backlog are missing (status : new for example) and others are showing but i don't want them here (status at pending, accepted or corrected).

The filter used for this board is (same filter than the kanban board we used to have):

project = XXX_RQM AND "Business value2" is not EMPTY ORDER BY Rank ASC

Do you have any ideas why i can't see the issues in "new" status and why I see issues on "pending" status in the backlog ?

Accepted answers

Rudy Holtkamp

Hi @LAMBERT Emilie and welcome to the community,

Could it be that you did not map all statuses on the board columns?

Go to your board > ... (in the upper right corner) > Configure board > Columns

In the example above, you can see that the 'completed but not closed' status is not in any of the board columns. So you need to drag and drop it to an existing column or create a new one and place it there:

I hope this helps.

Rudy

PS The above picture is a Kanban board config, but a Scrum board will look more or less the same, except for the Kanban backlog column.

All comments

Yusuf K_nhc4hz

It sounds like the issues you're experiencing with your Scrum Board in Jira are related to the board's filter configuration. Since you've switched from a Kanban to a Scrum method, the visibility of issues in different statuses might need to be adjusted. Here's what you can check and possibly modify to resolve the issue:

Check the Board Configuration: Go to your board settings and review the filter query used for the board. Since this filter was originally set up for a Kanban board, it might not be correctly configured to reflect the workflow of your Scrum board.
Modify the Filter: The current filter might not include issues in the "new" status or incorrectly includes other statuses like "pending," "accepted," or "corrected." You can modify the filter to explicitly include or exclude issues based on their statuses. For example:

project = XXX_RQM AND "Business value2" is not EMPTY AND status in (New, Pending, Accepted, Corrected) ORDER BY Rank ASC

To exclude statuses, you might want to change it to:
project = XXX_RQM AND "Business value2" is not EMPTY AND status not in (Pending, Accepted, Corrected) ORDER BY Rank ASC

This will ensure that only items that are not in "Pending," "Accepted," or "Corrected" statuses are shown.
Review Status and Workflow: Ensure that the statuses used in the Jira filter match those defined in your project's workflow. Sometimes, statuses may not appear because they are not mapped correctly in the workflow associated with the new board.
Permissions and Visibility: Check if there are any permission schemes or issue security settings that might be preventing certain issues from being visible on the new Scrum board.
Consult the Workflow Scheme: Since the Scrum board relies heavily on the workflow to function properly, make sure that the workflow scheme for your project correctly reflects the process you want to follow for the Scrum methodology.
Clear the Board's Cache: Sometimes, boards may not update correctly due to caching issues. You can try clearing the cache (if applicable based on your Jira setup) or re-indexing the project to see if that resolves the issue.

Rudy Holtkamp

Hi @LAMBERT Emilie and welcome to the community,

Could it be that you did not map all statuses on the board columns?

Go to your board > ... (in the upper right corner) > Configure board > Columns

I hope this helps.

Rudy

PS The above picture is a Kanban board config, but a Scrum board will look more or less the same, except for the Kanban backlog column.

Rudy Holtkamp

Above might be an answer to your first question:

The second part of your question "why I see issues on "pending" status in the backlog ?"

The issue you see in the backlog with the pending status is visible because, Pending is mapped to one of the columns of the board, but does not a sprint assigned to it.

So if you create a sprint and assign it to the Pending issue it will be either in that sprint or if the sprint has started it will be visible on the sprint board.

LAMBERT Emilie

To complete my post, my workflows and columns are the same than our previous board & the status pending & corrected are indeed mapped in some column in the scrum board so I really don't know how they can be in the backlog

column board.png

Rudy Holtkamp

Then they issues are not assigned to a (started) sprint.

Just open a 'Pending' issue and look at the sprint field, it is most likely empty

That is the reason why you see it in the backlog.

Only issues with the current running sprint in the sprint field are visible on the sprint board. All other issues, are in the backlog or in not-started sprints.

In the above picture you see my Backlog page.

In this picture you will see the active sprint (Sample sprint 6), 2 future sprints (Sample sprint 7 & 8) and the backlog (all issues that do not have a sprint assigned).

In the backlog you will see issues that are 'In progress'. In your case 'Pending'.

When you complete a sprint, Jira will ask what you want to do with all open issues. You can move them to another (existing or new) sprint or move them to the backlog. This is regardless of the status.

I hope this give you some understanding about issues, sprints, backlog & statuses.

LAMBERT Emilie

Thank you all for helping, my problems came from 2 things:
- the status "new" was not mapped so I cound't see the issues in that status in the backlog

- the issues that have a status mapped in the column of the scrum board weren't in a sprint (active or not started)

Rudy Holtkamp

👍

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

status

backlog