Epic issue type does not show up in my backlog, but Capability and Feature do

[Jessica Ren]

I created a Kanban board and a scrum board using the same project. This project has this hierarchy: capability, feature, epic, story, sub-task. The Kanban board is to show all the issues on this project, and the scrum board is used for a subset of the issues, which are all children of one capability issue.

So far I only have capability, feature and epic for this subset. I used this filter for this scrum board: 

issue in portfolioChildIssuesOf("ABC-123") or issue ="ABC-123" ORDER BY Rank ASC

ABC-123 is the capability, the highest level of all these issues. This filter returns all the 3 issue types mentioned above, but on the scrum board, I don't see any epic. In the epic filter on the scrum board, I do see the epics listed there, but I want them to show up explicitly in the backlog.

Why? How can I fix this? Thanks!

[Walter Buggenhout · Accepted solution]

Hi @Jessica Ren and welcome to the Community!

I'm afraid you, can't - unfortunately. In a scrum board, Epics are always displayed in the epic panel in the backlog, where they act as the level to filter the underlying stories by for sprint planning. It is the story (and sub-task) level issues that are added to the sprint for your team to work on.

Hope this clarifies!

[Ana Vitória Selista]

Hi Jessica,

Epics do not appear in the Scrum backlog or board like other issue types (e.g., stories or tasks). Instead, they show up in a separate Epic panel on the left side of the backlog. Jira treats epics as containers for other issues, not as sprintable items, so they don't appear in the main backlog or board.