-
Suggestion
-
Resolution: Won't Fix
-
29
-
49
-
Hi everyone,
To ensure consistency, the Backlog will treat all epic level issue types the same - this includes the epic level issue type provided our of the box, as well as any epic level issue types that you create.
Regards,
Eoin
Product Manager, Jira
After this https://jira.atlassian.com/browse/JSWCLOUD-25522 was released, the custom epic issue type is being recognized by the epic panel in the backlog, so these custom epics no longer appear in the backlog.
The customer wants to be able to choose whether or not this issue type will be considered in the Epic panel or not.
[JRACLOUD-90591] Treat custom epic issue types like a base level (e.g. task, story) issue types in the backlog
This affected us too. We also use a customer epic issue type and attach these (via parent) to other tickets at different places in our hierarchy. It is vital to us that we can see them on the backlog / board as peers of Story, Bug etc.
Personally I would like the Epic view in boards to replaced. I would like Epics (and similar types) to appear in the normal backlog, and be able to expand / collapse them to show the issues within them. The seperate epic panel is unhelpful to me - it is basically just like a filter. I want a true hierarchical view.
Thank you for rolling back on 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.
Hi all, I apologise for the inconvenience caused by the disruption due to this fix in JSWCLOUD-25522.
We have decided to address this 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 this bug ticket JSWCLOUD-25522 open. 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.
We need to display custom epic issue type in backlog as cards in a scaled context.
And anyway not consistent : any custom issuetype at "Initiative" level, so upper than Epic in hierarchy, is displayed in the Backlog as cards 
For Atlassian PM : we need a way to consider Epics(custom Epics) as card or as panel, like in Kanban boards as an option, but for Scrum boards. It will cover every need imo
Custom epic issue type being restricted to left panel reduces the team's ability to manage these items effectively in backlog. Please provide an option to either make it visible in backlog or side panel.Thanks
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use Jira so we can continue improving your experience. To uphold our value for transparency, we wanted to provide an update that we have no immediate plans to put this suggestion on our near term roadmap.
To recap on this topic, in July 2024 there was a change to treat custom epic issue types to make them behave like the epic issue type that is provided out of the box by Jira. This was the original intended behaviour and we apologise it was done subsequent to the initial rollout of custom epic issue types. We don't expect to change this behaviour in the near term.
We understand that our decision may be disappointing and we apologise for any inconvenience.
Regards,
Eoin
Product Manager, Jira