Mapped Statuses Not Displaying on Board

[Christina Williams]

While configuring a board in a Team Managed Project, the board does not display issues with mapped statuses as expected. There are no filters, and I've cleared my browser cache. All statuses are mapped in the board configuration but issues with the corresponding status do not display on the board. Any suggestions or workarounds?

I've reviewed other threads with this issue, but I'm not finding a solution:

https://community.atlassian.com/t5/Jira-Software-questions/JIRA-Version-Display-not-mapping-issue-status-correctly/qaq-p/836195

Board Config View:

Board User View:

Oddly enough, if I create a new issue FROM the board, with a backlog status it displays as expected. However issues NOT created from the board do not display.

[Trudy Claspill · Accepted solution]

Hello @Christina Williams 

Welcome to the Atlassian community.

Is the project a Software project or a Business/Work Management project?

What is the issue type for the 30 issues that the mapping page says are in the Backlog status?

Is the board a Scrum board or a Kanban board?

[Christina Williams]

Hi Trudy, 

Software Project, issue type = task, Scrum board

Story issue types are affected as well, but in this case it's task. The task created from the board is the only one that displays on the board view.

[Trudy Claspill]

I think you edited your post to add that last part as I was posting my response.

If you are using a Scrum board then when you create an issue using the Create button in the menu bar, the issue will go to the Backlog. It will not automatically be added to an active sprint on the board.

If you are using a Kanban board and have enabled the Backlog screen then in that case also using the Create button from the menu bar will put the issue into the Backlog, not the board. From the Backlog screen you have to move the issue from the Backlog list section to the Board list section above it. Using the Create option within the board column will automatically add the issue to the board.

That is different behavior than what you would see with a Kanban board in a Company Managed project. In a CM project that has a Kanban board and Backlog screen, positioning the issue in the Backlog list or on the Board is based on the issue status. That is not the case with a Team Managed project. An issue can be in any status and be in either the Backlog list or on the Board.

[Christina Williams]

Got it. That solves the mystery, thank you! Is there a way to change the project type from Scrum to Kanban? I already disabled sprints as we don't need the functionality.

[Trudy Claspill]

In a Team Managed project you can switch between Scrum and Kanban by turning the Sprints feature off.

With that off you also have the option to turn off the Backlog screen feature, so that you have only the Board display.

[Bastien Delourmel (FMX)]

Hi @Christina Williams

Do you have any tickets in "Backlog" ? 

They might be there 

[Christina Williams]

Yes, I can view them in backlog but not on the board view

[Bastien Delourmel (FMX)]

Ok, you might need to drag / drop them into the backlog in a way to see them, then start the sprint

[Christina Williams]

Thank you! That's what Trudy suggested as well and I got it to work :)