Within Issue type hierarchy setting it seems only possible to create parents for Epics.
We are trying to have multiple issue types at the same hierarchy level than Epics...
Solved! Go to Solution.
we were planning to have product managers using Advanced roadmaps and work on the needs there, then have engineering translating them into epics and stories.
How could we achieve that if we don’t have a "requirement" issue type attached to a portfolio features, besides the epics?
To clarify the idea was to have that requirement during the maturation / requirement gathering phase then the epic created once the work to be done was well scoped and executable.
@Ghislain BourginYes, but this could depend on what additional plugins from atlassian marketplace your company may be running in the background.
Based on your screenshot, you should have the option to click the Jira Issue Types dropdown at hierarchy level named Epic (i.e., # 1) and start adding additional issue types as desired.