How do I get Epic level issues to appear in the Backlog epic panel

[Chris Saunders]

I've created several Epic level issues to help group and distinguish between the various applications for an Epic we have.

These new issue types behave like an Epic in nearly all aspects except they dont appear in the Epics drop down or panel for the backlog view.

They appear as expected in the dropdown when viewing an active sprint board

This feels like a bug, it makes them hard to quickly find in order to filter a backlog.

[Trudy Claspill]

Note that there is a 10 year old change request in Atlassian's backlog to fully support having multiple issue types handled the same way as Epics.

https://jira.atlassian.com/browse/JRACLOUD-80492

[Mark Segall]

Hi @Chris Saunders - The issue type hierarchy is only relevant to Advanced Roadmaps.  Epics have a very specific characteristic to them that makes them unique from all other issue types even if they reside at the same level of the issue type hierarchy. 

In these cases, I typically ask why you need to have multiple issue types sharing the same level?  You can delineate between your different types of Epics by using metadata like custom fields, components, or labels or leveraging epic coloring in the board.

[Chris Saunders]

This stuff could be made more obvious :)

Mainly, I prefer this functionality as it's easier for our team to administrate as the specific uses for each type are self describing. And, in most respects the functionality works fine!

It'd be a two stage process (room for error, as it can't see how it could be automated) to use an additional means to define the purpose.

Thanks,

Chris

[Mark Segall]

This stuff could be made more obvious :)

Agreed.  Not many people realize that like many of Jira's features, Advanced Roadmaps started out as a marketplace app.  As Atlassian continues to further integrate their acquisitions into the Jira core it can create intermediate confusion like what you're facing.

Mainly, I prefer this functionality as it's easier for our team to administrate as the specific uses for each type are self describingIt'd be a two stage process (room for error, as it can't see how it could be automated) to use an additional means to define the purpose.

I understand the mindset and the challenges you'd face with change management, but Epics are designed to be the catch all "container issue type" with those added features so I would recommend reevaluating the issue type strategy to see if you can make it work in your environment.