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 of certain statuses not displayed on board although found by the board filter.

Christian Sieber

Hello everybody,

we've enhanced our story workflow by adding new statuses. Although issues having these statuses are found by the board filter (validated on "Search for issues" page), none of these statuses are displayed on the column-configuration-page of the board.

We've re-indexed the project already.

What may be the reason for that?
Thanks for your replies.

Accepted answers

Christian Sieber

Our consultants found an official bug report describing the situation. There is also a workaround provided, which works for us: JSWSERVER-11623

Therefore I'll mark this as an answer.

All comments

Jack Brickey

Have you mapped these new statuses to columns on your board? Go to board settings then columns and check if you see statuses that are unmapped that should be mapped.

Christian Sieber

Hello @Jack Brickey

thanks for your reply and your time.

A mapping of these new statuses is not possible as these new statuses are not displayed in the unmapped status list at all.

Jack Brickey

But you are sure the new workflow is published? It would seem so based on you stating the board’s filter displays issues with new statuses. I cannot understand why the new statuses would not be showing in either the unmet column or one of the board columns. Just for grins I wonder if you create a new board what the results would be.

feel free to share screenshots of board, filter and column views.

Christian Sieber

Hello @Jack Brickey , yes the workflow is published, as the issue (=story) can be transitioned to the status we want.

I could narrow down the situation:

When I create a new scrum board from scratch from an "existing project" the statuses are shown in the board configuration.

Next I checked the board's filter, again. It is:

project = PROJECTID AND NOT (type = Story AND status = OPEN) AND (sprint != 8852 OR sprint is EMPTY) ORDER BY Rank ASC

When I strip to

project = PROJECTID AND (sprint != 8852 OR sprint is EMPTY) ORDER BY Rank ASC

the missed statuses are shown in the unmapped status column in board configuration and the missed issues in the board itself.

This situation seems strange to me, because the Story I used for this scenario has status "Ready for Storytime" but not "Open"

Christian Sieber

Our consultants found an official bug report describing the situation. There is also a workaround provided, which works for us: JSWSERVER-11623

Therefore I'll mark this as an answer.

Jack Brickey

Nice! Thanks for sharing here

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-software

jira-software-server