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

Issues disappearing from board and backlog, when enabling Kanban backlog

Simon Fyhr

EDIT: Epic panel was turned on by mistake, thus showing all epics (in a board of only epics) in the panel rather on the board itself.

I have created a kanban board, to show all my Epics.

The filter used is:
project = X AND issuetype in (epic) AND "Custom field1" in ("TeamName") ORDER BY Rank ASC

We have 6 possible statusses for en epic, and 5 coloumns on the board. Thus, we have used the kanban backlog for the remaining status.

Today the board suddenly showed no issues at all.

The only change we can think of, is that we have changed the name of the status used in the backlog.
This was done by adding the new status to the workflow, transitioning all issues with the old backlog-status to the new backlog-status, deleting the old backlog-status and adding the new backlog-status to the backlog in the board.

We have two other boards, with exactly the same setup, except they use another TeamName in the filter. These do not have any issues after this change.

While trying to find the issue, I discovered that by removing the status from the backlog (thus disabling the backlog) I can get all tickets to be shown correctly. However, when I activate the backlog again, no issues are found in backlog or board.

Why does the activation of the kanban backlog make all issues disappear from the board?

Picture 1. When the backlog-status is set to be shown in first column of the board, all issues across all columns are on the board

Picture 2. When the backlog-status is set to be shown in backlog, no issues are shown in any column or backlog

Picture 1
"Ide" status in first column = all issues seen on the board, including the ones with status = "Ide".
The same can be accomplished by removing "Ide" status altogether from the board. In this case the issues with status = "Ide" is not visible on the board (as expected).

Picture 2
"Ide" status in backlog = no issues on the board or backlog

I hope the smart people in here can tell me what I am missing

Note, I have tried creating a new board based on a new filter (with the same JQL). This has exactly the same issue.

Accepted answers

Simon Fyhr

Sometimes, the answer is right there.

Turns out that we had activated the "Epic panel" by mistake. Thus making all epics show in the epic panel when the backlog is present.

Since it is a board with only epics, nothing was shown on the board or the backlog.

The lesson to be learned: Check the simplest possible explanation before venturing into the depth of what could be wrong.

All comments

Fabio Racobaldo _Catworkx_

Hi @Simon Fyhr ,

welcome to the community!

Beacase you activated backlog, ticket in board should be added in the backlog mane first otherwise they will not appear.

Take a look to the following documentation for further details Using your Kanban backlog | Jira Software Data Center and Server 8.13 | Atlassian Documentation

Hope this helps,

Fbaio

Simon Fyhr

Hi @Fabio Racobaldo _Catworkx_
Thank you for the response.

I cannot see that an issue needs to be created from the backlog in the documentation you refer to. Could you be more specific?

We have multiple epics in each status, both backlog (="Idea") and the 5 statusses shown on the board.

Even if I test it, by creating an epic directly in the backlog, it does not show (see below screenshot).

Simon Fyhr

For reference, one of my other epic boards, set up in the exact same way, does show everything as expected.

Fabio Racobaldo _Catworkx_

If you don't see new issue created on the backlog you need to check board filter first.

Please, let me know,

Fabio

Simon Fyhr

Sometimes, the answer is right there.

Turns out that we had activated the "Epic panel" by mistake. Thus making all epics show in the epic panel when the backlog is present.

Since it is a board with only epics, nothing was shown on the board or the backlog.

The lesson to be learned: Check the simplest possible explanation before venturing into the depth of what could be wrong.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server