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
We've instituted Advanced Roadmaps and are very excited about all the possibilities it holds for our roadmaps and planning. However, we cannot see how to remove the initiatives from the backlog (it clutters up our view), without amending the filter query to include the JQL condition issuetype != initiative
Is there any way to treat initiatives (and themes if we use them in the future as another level of hierarchy) similarly to the epics view on a scrum (or scrumban) backlog?
To avoid this problem, I created a separate project in Jira, called PLAN, to include all "higher level" custom issue types that aren't included in sprints. This was actually a recommendation in the old Portfolio for Jira documentation, I believe.
In the Plan, I bring in both the PLAN project and the actual project being tracked.
This approach gives the added benefit of having all initiatives (a collection of epics) centralized in one project.
I hope this helps.
I/we do the same as what @Joe Lagana-Jackson has suggested.
This centralised approach to the high level "Initiatives" also makes it easy for senior leaders to find them and puts them all in the same backlog/funnel.
I encourage it as the best, scalable option.
You can achieve this within Advanced Roadmaps in a few different ways:
1. You could configure your plan to exclude the Initiative issue type (configure -> exclusion rules):
2. You could visually remove these from your timeline using the hierarchy filter (go to filters -> select the level below initiative as the from hierarchy level):