nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to exclude initiatives from the backlog without amending the filter query?

Danielle Green_1lthiv

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?

Accepted answers

Joe Lagana-Jackson

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

Curt Holley

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.

All comments

Joe Lagana-Jackson

Hi,

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

Curt Holley

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.

Emma Ysebaert

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

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

Happy planning!

Emma

Daniel Turczanski - JQL Search Extensions

A lot of project managers end up using our JQL function childrenOfIssuesInQueryRecursive in a setup like that.

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

King Yiu Chu_w7xmom

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!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

atl-gruland

advanced-roadmaps