Thank you for fixing this. We need to use custom epic issue type (epic hierarchy level) and if possible also the upper level (Initiative) and be able to see it on the backlog board. It is vital to our workflow. I think epic-level issues should also be visible on sprint boards if possible.

Thank you guys for implementing my initial request. That is the huge step forward toward Jira supporting those parent links relationships you introduced couple years ago.

Hi all, I apologise for the inconvenience caused by the disruption due to this fix.

We have decided to address the feature request JSWCLOUD-26916, so there will be an option to display custom epics as cards on the Scrum backlog, instead of in the Epics Panel.

In the meantime, we will close JSWCLOUD-25522. If you are impacted by this fix, please submit a support ticket and ask for it to be disabled in your instance. Once JSWCLOUD-26916 is done, we will publish documentation on the new behaviour, and enable this fix again for your instance.

df8efda53dbe my feedback is:

When you select a Version filter, let´s assume I have a Release called PI2 and this release is assigned to each item with the field "fixversion" (also the old EPIC by us now called Features). In this case I expect only to see a filter result with  the Features which belongs to the release/version PI2, also in the left navigation field. Current behavior is that in the left navigation all items will be displayed independet from the Version / Release Filter.

This is, what I expect from Atlassian if it should be fully fixed.

Since they moved from Epic Link to Parent Link Type they should support all custom Issue Types (i.e. Feature) to be used in all kind of Boards (Kanban, Scrum and their Backlogs) like you currently do with Epics.

750c3ee75cc3 Are you saying that once the bug is fully fixed, that we will be able to manage custom Epic Issue Types in the backlog like any other issue type except for Epics? 

HI df8efda53dbe  the bug is only partly fixed, the version filter is not considered in the left Layer1 Navigation bar and in the filter for Layer 1. 
Expected behavior if you select a Version only the to the Version assigned Items will appear./ will be displayed

Hi, 

This change is impacting our ability to apply SAFE appropriately in the backlog for Epic management. Can we pls have an option where we can still have custom epic issue types as being separate to that of Epic? Thank you!

Attached request is here: https://jira.atlassian.com/browse/JSWCLOUD-26916

Our team uses the backlog view to update and manage custom epic types. Moving these issues to panel on the left side makes management of these types harder. Can't this fix be managed a bit better by moving the custom epic types to side panel only if the "Show Custom Epic type Panel" is selected else can't the Custom Epic types issue be still showed in the backlog.

we have the same issue working in safe essential and require Feature/Enablers instead of EPIC´s on Level1. See also a related bug here: https://jira.atlassian.com/browse/JSWCLOUD-26266