Add/Change Epic renamed to Parent Issue

[Cody_Bennett]

We are using a Next-Gen Project, previously when editing/viewing an Issue we can add an issue to an Epic, or change the Epic if it was already in one. That is still possible however it now presents itself using a Parent Issue dialogue. 

[Angélica Luz · Accepted solution]

Hi Cody,

The next-gen and new issue view is constantly changing and this was part of the latest updates.
Currently, only the filter on the board and backlog still shows as Epic, but we already have a feature suggesting to change it to Parent issue:
- https://jira.atlassian.com/browse/JSWCLOUD-17906

Regards,
Angélica

[Cody_Bennett]

Accepting this as answer, however I personally disagree with the change from Epic to Parent Issue and would prefer, at the very least, and option to select verbiage. 

[chris.foster]

I agree. Why the inconsistency with naming?

[Dan Checovetes]

@Cody_Bennett @chris.foster This is going to allow much more flexibility when it comes to the issue type that stories roll up to.  Take the example of a SAFe implementation in Jira.  SAFe terminology says that stories roll up to Features, not Epics.  An issue type of Feature can now be created and stories can roll up into them using the more generic "Parent" field, instead of Epics that Jira currently forces you to use.  You can, of course, still use the Epic issue type if you want, it's just the name of the special field that will be different.

[Ora Zyto]

Meanwhile.... I am pretty proficient with Jira in general, and I've just spent more than a half hour trying to figure out why our option for "Add to Epic" had disappeared from our options.

Please fix this - use Epic again - or at a minimum customization!

There was no information whatsoever on this incompatibility change. "parent" does not scream "epic" to me. Very disconcerting. 

[Angélica Luz]

Hi everyone,

The change of the Epic to Parent issue occurred due to the release of Sub-Tasks and Jira Software Premium.
It was changed because it could be confusing if you change the parent issue of a sub-tasks or to manage the hierarchy (which is a feature from JSW premium) and assign the issue to a different issue type on the hierarchy layer.
Even though the name has changed, the functionality is still the same.

Regards,
Angélica