How to exclude initiatives from the backlog without amending the filter query?
Asked by Danielle Green:

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?


Answers:
author: Joe Lagana-Jackson
body: Hi,

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.

Joe

comments: author: Daniel Turczanski - __JQL Search Extensions
body: A lot of project managers end up using our JQL function [childrenOfIssuesInQueryRecursive](https://jqlsearchextensions.atlassian.net/wiki/spaces/SEARCH/pages/3375124/JQL+aliases+and+functions+reference#ChildrenOfIssuesInQueryRecursive) in a setup like that.

Just keep in mind it's there once you need it.


author: Curt Holley
body: I/we do the same as what [@Joe Lagana-Jackson](/t5/user/viewprofilepage/user-id/3486626) 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.


author: Emma Ysebaert
body: Hi Dani,

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**):

![Screen Shot 2021-10-14 at 11.18.52 am.png](https://community.atlassian.com/t5/image/serverpage/image-id/164848i7925C3263A57AFDB/image-size/large?v=v2&px=999 "Screen Shot 2021-10-14 at 11.18.52 am.png")

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):

![Screen Shot 2021-10-14 at 11.21.03 am.png](https://community.atlassian.com/t5/image/serverpage/image-id/164849i3C2F4CD985B9E0F3/image-size/large?v=v2&px=999 "Screen Shot 2021-10-14 at 11.21.03 am.png")

Happy planning!

Emma

comments: author: King Yiu Chu
body: You don't have to create a separate project in JIRA to include Initiatives on your JIRA Plan overview as described above...

Just add the filters on your project board for your development team. (Just add to the filterline "AND (Issuetype != Initiative)".

After you added the filter **it will remove the initiatives** from your backlog **but it will also remove it from your JIRA Plan overview** . ++**To include it on your Plan overview**++:

1. Create a new Board on the same project.

2. Add a filter to this board where you ONLY show Initiative issuetypes.

Now your JIRA Plan overview will show the full hiearchy of Initiatives and it's connected EPICS in the same project.

Job done!


Tags: advanced-roadmaps