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
My question is a follow up to the following Atlassian Community post:
If a custom issue and issue hierarchy is defined using Advanced Roadmaps, is that configuration fixed for every project developed across the organisation moving forward? I would like a custom issue and issue hierarchy for my team, but I would not want to impose this setup across the broader organisation.
Advanced Roadmap Issue Hierarchy setup is at per site basis. However, you can have multiple issue types defined at the same level in the hierarchy configuration.
Initiative is normally setup to a parent of Epic, you can implement another issue type to be at the same level as Initiative (i.e. Functional Area Goal). This will allow you to handle different areas needs. The drawback of this is that you will need to keep on top of the setup and control it not going over-board just because a team/area doesn't like to use Initiative to roll-up their Epic.
Hope this give you some ideas.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team