I created a new "company managed project" and an epic in it. I created issues in the epic using the link in its box but none of them show in the backlog. They are under the epic when I click on it: And they show in all issues: So why can't I see them in my backlog? This is my workflow:

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 not showing in backlog

Michele Daigle

I created a new "company managed project" and an epic in it. I created issues in the epic using the link in its box but none of them show in the backlog. epic create issues.png

They are under the epic when I click on it: issues in epic.png

And they show in all issues:

all issues.png

So why can't I see them in my backlog? This is my workflow:

Accepted answers

Trudy P Claspill

Hello @Michele Daigle

What is the filter for your board?

Can you show us the Columns page under Board Settings?

This issues may not be appearing because

- they are being excluded by the filter used by the board

- the status that the issues are in is in the Unmapped section in your Columns page.

All comments

Trudy P Claspill

Hello @Michele Daigle

What is the filter for your board?

Can you show us the Columns page under Board Settings?

This issues may not be appearing because

- they are being excluded by the filter used by the board

- the status that the issues are in is in the Unmapped section in your Columns page.

Airbus Driver

This seems to be relevant to Why must we map a given status to a column in order for the issue to appear in Scrum backlog?

Michele Daigle

I'll go get that now, but I do get this msg when I create a story in or out of an epic not showing.png

Michele Daigle

here are my columns, it is a sprint not kanban board so I don't want a backlog column in my sprint. No matter the status, they won't show on the backlog either.

Michele Daigle

And that doesn't fix that user's issue or mine. I don't have this issue with my three other projects/boards either?

Michele Daigle

It's asinine but this worked:

bl workinhg.png

Michele Daigle

Thank you for helping out!

Airbus Driver

Thank you, Michele for updating the post with your solution

Yatin Shingala

Even the issues having status which is mapped to the right most column will also not visible in the backlog. So, don't map the status to the right most column.

Arturo Chavira Pacheco

I got the same issue, You find any fix to this?

Trudy P Claspill

@Arturo Chavira Pacheco

Welcome to the Atlassian community.

Please consider starting a new post/Question for your issue and provide all the relevant information for your scenario such as your hosting type (cloud vs. server vs. data center), the type of board (scrum or kanban), a screen image of your Columns configuration, a screen image of your backlog screen, and details about which issues are not displaying.

Sarah Gentry

**Jira Cloud user: This has already being said, but the work around and logic is that you have to map a workflow status under a column. So if you have workflows that are intended as pre-sprint activities, then as long as you don't add the issue itself to the active sprint your issue will not show up on or in your sprint, and you will see it in your backlog. My todo column has essentially become a junk yard, but that's okay.

I feel that all workflows (unless specified otherwise) should show in the backlog view regardless of them being mapped on columns, because I want columns exclusively for what I have in my sprint. So I am not a fan of what the work around has to be when you are using custom workflows that are meant to be completed prior to the sprint.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

atl-gruland

backlog