This Bug is Cloned from the server version of this BUG JPOSERVER-2703, With slight differences in the Epic issue type behavior.
When you are creating an issue in an epic the option for initiative hierarchy levels (the level above an epic per portfolio hierarchy configurations) is also listed in the create dialogue as an option to be created as the level below the epic, as the Initiative can be mapped to the Epic as the parent, in turn could lead to additional errors such as a related Server platform BUG JPOSERVER-2691 (Which currently only affects the Server version of the application at this time and not known to affect the cloud version) as a conflict occurs because the initiative cannot be both the parent and child of an Epic at the same time, but similar behavior could occur, and the mapping should not be possible.
- make sure a hierarchical level above epic exists (initiative)
- Navigate to an existing Epic
- Use the "Create issue in epic" option
Only standard issue types that are not mapped to an initiative hierarchy are listed in the issue type field.
The Initiative issue types are listed as avaliable issue types, and the Initiative can be selected and created as a child of the Epic
As the Initiative is considered a standard issue type but mapped to the higher hierarchy levels by portfolio the mappings would be possible if Portfolio was disabled, so an additional Expectation could be that a warning or error would occur when a initiative issue type is selected noting the issue types are invalid because of hierarchy configurations
You can use the following JQL to identify issue in this state:
perform Bulk Update to remove the Epic link