You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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...
HI @Sylvain Baron welcome to the Atlassian Community!
At the moment, Atlassian is working on that feature I believe.
Right now, in Advanced Roadmaps, you cannot have more than 1 issue type (by default Epic).
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.