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
Hello My plan does not take into account the Epic of my project. Knowing that in fact in my project the system issue type was renamed to Feature and we created another type Epic. And so a feature behaves like an epic.
Is there a workaround to take into account my epic?
Hi @alice lowah
You may have jumped the gun a bit with the renaming of a Jira Epic to feature.
How old is this Jira instance? I ask because if you had a lot of existing data making use of the epic link field, that relationship is now pointing at your features, not your new Epics.
Also, you need to update your Advanced Roadmaps hierarchy and make use of the parent link field to associate the Features with these new (higher) Epics to visualise them in Advanced roadmaps
Are you using Cloud or Server?
I'll presume cloud and recommend you read this: Rename ‘epics’ in your company-managed projects (atlassian.com)
Thanks @alice lowah
In that case I would recommend talking with the Admins, or if you are one, then studying the issue types, and their relevant schemes and permissions for insights.
Sorry, I only have access to Cloud so can't even try to play around to assist.