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

Jira Tickets are not appearing on boards

Hannah O'Sullivan

Not all tickets are visible on the board, they are not showing in the backlog section and are also not searchable.

Email confirmation is coming through and some tickets are coming up in the notifications but not all.

Could you please advice how can this problem be rectified?

Accepted answers

Jack Brickey

Hi @Hannah O'Sullivan , welcome to the community.

What displays on your board is defined by the underlying filter defines your board. So if issues for not showing that is most likely due to the fact that the filter is excluding those issues. Can you please share more information about your board, specifically the filter. I am assuming this is a CMP project and as such you can find the underlying filter by clicking on the… in the upper right corner, selecting board settings and go to the general tab and look for your bored filter.

All comments

John Funk

Hi Hannah - Welcome to the Atlassian Community!

Check the board filter to see if it is limiting what issues you are seeing on the board.

Go to Board Settings > General

Also take a look at the bottom of that tab to see what the Sub-filter might be restricting.

Jack Brickey

Hi @Hannah O'Sullivan , welcome to the community.

Hannah O'Sullivan

Hi Jack,

Thank you for coming back to me. I'm unsure what is meant by the filters as there are no filters to select when creating the ticket. Also, I went from being able to create a ticket to not. I don't have an option of board settings or general, so I'm finding it hard to follow the advice given.

Hannah O'Sullivan

Hi John,

As far as I'm aware there are no filters selected and I don't have the buttons Board settings or General and so I'm struggling to try and use this advice, are you aware of anything else I can try?

Nic Brough -Adaptavist-

Filters are defined searches that return a list of issues matching the question. They don't get put on issues, they are used to find and report on issues.

Boards (and backlogs) use them in the background to decide what issues to present to you.

If you do not have "board settings" or similar under the ...more or ... towards the top right of the board display, then there are two possibilities:

You do not have the admin rights to manage the board
The board is not a type that has settings (business board, or team-managed)

In the first case, you'll want to take these questions to the person who set up the board, or the owners

In the second case, the board is tied to a project, so the board filter that you can't get to is simply "Project = XYZ" - the board will be selecting all the issues in a single project.

John Funk

So, can you provide more information then. What type of project is it? Can you share a screenshot of the board without sharing an sensitive information?

Hannah O'Sullivan

Hi @Nic Brough -Adaptavist-

Thank for your response. The board is tied to a project. However, I can't seem to see what must be done to get the issues to appear automatically again once they are created. Any further advice would be great.

Marko Rogan

For me, deactivating the "Backlog" feature in Project settings -> Features helped (also team managed project)

Newly created tickets (with To Do status which was default) never showed up on the board even tho that first column was configured to show all tickets with To Do or any status that is not mapped for some other columns on that board.

Also there was nothing under the "unassigned statuses" column and To Do column did show 3 tickets but only when you're in Project settings -> Columns and statuses, but outside the settings, when you're on the actual board, To Do column was completely empty and didn't show those tickets.

They would show up there only after you assign that ticket to someone else or update something in the ticket. Until then, they were just hiding in the backlog so I removed the backlog itself and it worked.