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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
My company is learning more about Advanced Roadmap Planning and while several PM's and Jira Admins have watched various demos and webinars on the inner workings we are considering how to best configure our instance.
We currently have added Initiative issue type above Epics for the hierarchy. We have some PM's who think they would like initiative issue type associated to each of the projects their teams use and we have other PM's who think a dedicated project for initiatives would be best.
Is there a best practice in how to create/track initiatives or is it a "it depends" situation. What does it depend on.
Hi @Christine Byrer
I agree with @Wade H there is no right way, just the right way for you/your company.
That said, I am fond of separating out any levels above Jira Epics and keeping the team/standard projects with just the standard Jira hierarchy of Epic, Stories/tasks whatever/Sub-tasks.
Thank you for the feedback. In separating out any levels above Epics. If there were 2 levels above Epics would you separate out both of the 2 levels each in their own projects. So for example, a project for initiatives (first level above epics) and a project for objectives (second level above epics).
@Christine Byrer I think it would depend on how you plan to report on them.
In my opinion it makes it easier if they are in different projects for different levels of Hierarchy Or if you have different users handling backlogs.