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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have created a new Initiative issue type as described here and it look good, even if i wonder what the number in the first column means:
It seems to apply properly in Advanced Roadmap view:
But then I am checking the newly created Issue Typ via REST:
And the hierarchyLevel for the Initiative type is zero even If I expect it to be 2 (one higher than Epic). As A result I cannot create an Epic with an Initiative Ticket as a parent. This is a bit confusing.
Any Ideas ??
Thanks,
Florian
Thank you for your reply.
I changed the Issue type order as you mentioned, which affects the order of issue types in the REST service. I put Initiative on the top, followed by Epic.
But the hierarchyLevel remains the same: zero
other ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Florian Bauer ,
try changing the order in the issue type scheme of the project as well.
Issue type scheme-> choose the scheme and edit it
Drag and drop the issue types in the order as necessary
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.