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

My newly creates issues have the correct status, but are not visible on backlog

Jessica Ren

I creates some new issues, and they all have "backlog" status. According to my board settings, these new issues should show up on my backlog, and I can also see that they are on the backlog in the column settings. However, when I go to the backlog, they are not there. What setting should I change?

Accepted answers

Trudy P Claspill

Hello @Jessica Ren

Are you working with a Company Managed project or a Team Managed project? It will say at the bottom of the navigation pane on the left.

Are you working with a Scrum board or a Kanban board?

Can you confirm you don't have any Filters activated on your Backlog screen (a.k.a. Quick Filters or Custom Filters)?

What type of issue did you create? Is it an Epic, a standard issue (story, task, bug), or a subtask?

If you are working with a Company Managed project can you share with us the Columns page for your board and the Filter Query for your board?

All comments

Trudy P Claspill

Hello @Jessica Ren

Are you working with a Company Managed project or a Team Managed project? It will say at the bottom of the navigation pane on the left.

Are you working with a Scrum board or a Kanban board?

Can you confirm you don't have any Filters activated on your Backlog screen (a.k.a. Quick Filters or Custom Filters)?

What type of issue did you create? Is it an Epic, a standard issue (story, task, bug), or a subtask?

If you are working with a Company Managed project can you share with us the Columns page for your board and the Filter Query for your board?

Jessica Ren

Thanks for the prompt response.

I am using a company managed project, and I create story issue type. It is a kanban board.

I found out the reason why it didn't work, but I don't understand why this is the reason.

I have some tickets for 2022, and we need to close all of them and start from a clean slate in 2023. We don't want to see these 2022 tickets anywhere on our board, so I wanted to update the board filter to exclude them with a label "2022" on these old tickets.

Since I'm not the owner of the board, I updated the kanban board sub-filter, where I added the condition that all tickets with label "2022" should not be included on this board.

This filter is the reason. Once I remove this filter, everything works fine.

Why does this filter impact my backlog? The new items I created don't have this 2022 label.

Trudy P Claspill

The subfilter impacts both the board and backlog views.

Can you share with us exactly what you new subfilter looked like when you updated it?

When you created the new issues did they have any value in the Labels field?

If you modified the subfilter to add something like

and Labels != "2022"

...then that would end up excluding any issue that had a "2022" Label as well as any issue that had no Labels values at all. Jira interprets that criteria as

"there must be at least one value in the Labels field, and none of the values in the Labels field may be '2022' "

To ensure that you retain both issues that have Labels that don't include "2022" and issues that have no Labels you would have to adjust the filter thus:

and (Labels != "2022" or Labels is empty)

Jessica Ren

Thanks! What you have is exactly what I had in the sub-filter. It is tricky that Jira would think there must be a label with the condition

and (Labels != "2022"

Your answer totally solves my problem. Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud