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
Here is the situation explanation:
Now, we need to add a new level "Feature" to improve the use of Jira:
What will happen with existing links between Epics and Stories for:
Any other issue that I'm not foreseeing?
Thanks for the help!!
Hello @Jonathan Huet Welcome to the community.
We can add the fourth hierarchy Initiative in Jira when we are using the Premium Packages. I'm currently using Standard package so Adding another hierarchy is not possible for me.
But Adding Initiative as a new hierarchy won't disrupt any features and EPICS.
Though any tickets will be left abandoned, you can still map them with your desired EPICS, and Features.
Though a Issue type scheme don't have Feature issue type, it doesn't mean that an issue cannot integrate with features. As soon as you add issue types in the issue scheme, than the existing features will be displayed. And the missing features can be added.
Thanks for the answer.
Feedback on the answer
In my case, the Initiative issue type is already added and part of the hierarchy, working like a charm.
Fine-tuning the answer
What I want to add, is a new issue type "Feature" and insert it in the middle of an existing hierarchy (between Epics and Stories).
What worries me, is what will happen with issues that already have the link Epic <--> Story:
Thanks for the help :)