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; } } }

Creating a Plan (roadmap) from a Filter

John Chanter

I'm trying to create a Plan/Roadmap from a filter that will allow full hierarchical display (Parent > Epic > Story) as I'm able to see when I create a roadmap from a project. Does anyone have an idea of what JQL query I'd use to create such a filter?

Accepted answers

Gautham Krishna

Hi John,

Adding a concrete query to what Trudy described. If your site has Plans (Advanced Roadmaps), there is a function that returns everything below a parent, at every level:

issue in portfolioChildIssuesOf("PAR-1")

It does not return the parent itself, and it takes one key at a time. For a subset of parents, add the parents back and join one call per parent with OR:

key in (PAR-1, PAR-2) OR issue in portfolioChildIssuesOf("PAR-1") OR issue in portfolioChildIssuesOf("PAR-2")

Save that as a filter and pick it as the source when you create the plan. The query itself does not need anything about the hierarchy. As Florian said, the plan builds Parent > Epic > Story from your site's hierarchy settings, as long as all three levels are in the results.

One thing to check: if the filter returns only the parent keys, the function is not available to you. On a site without Plans it does not show an error, it just returns nothing for that part of the query.

Hope that helps.

All comments

Florian Bonniec

Hi @John Chanter

The hierarchy in Plan/Advanced roadmap is not defined in the query you use. It's defined at the site/instance level. In order to have a filter that "works" you just need to include the type of issue that are associated with each level.

https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/

Regadrs

Trudy P Claspill

Hello @John Chanter

Can you confirm for us if this is Jira Cloud or Jira Data Center?

Is the hierarchy Parent > Epic > Story already configured and in use in your Jira projects?

For the Plan that you are trying to create, are all the issues within a single project? Why are you trying to create a filter as the source for the plan rather than specifying projects or boards as the source?

Are you trying to limit you plan to specific Parents and their child Epics and the Stories under those Epics?

John Chanter

Responding to Trudy:

I am trying to limit my plan to specific Parents and their child Epics and Stories under those Epics.

We do have that configuration under Jira projects, I just need a subset (mini-roadmap) for a small population.

I'm not sure about Cloud vs. DC - I'm a small cog in a hug wheel (BofA).

Thanks for anything.

Trudy P Claspill

Thank you for the additional information @John Chanter .

If you click the Help icon (the question mark) near you avatar in the upper right corner of Jira and select About Jira some info about Jira will display. Can you provide a screen image of that pop-up? If it shows a version number like 10.13.2 that is an indicator that you are using Jira Data Center. Jira Cloud does not show a version number like that.

How many Parent issues do you need to include? Do you have any apps that extend the JQL functionality, such as ScriptRunner, JQL Tricks, or other apps?

Neither Jira DC nor Jira Cloud has a simple native JQL function to get multiple Parents and all their descendants. Here is a link to information about functions that cross the Epic/parent of Epic relationship

…for Jira Cloud: https://support.atlassian.com/jira-software-cloud/docs/search-for-advanced-roadmaps-custom-fields-in-jql/

…for Jira DC: https://confluence.atlassian.com/advancedroadmapsserver/searching-for-issues-using-advanced-roadmaps-details-940678957.html

You would need to string multiple JQL statements together with OR to get a complete query result set that contains :
Parent 1 OR descendants of Parent 1 OR Parent 2 OR descendants of Parent 2 OR Parent 3 OR descendants of Parent 3…

Gautham Krishna

Hi John,

Adding a concrete query to what Trudy described. If your site has Plans (Advanced Roadmaps), there is a function that returns everything below a parent, at every level:

issue in portfolioChildIssuesOf("PAR-1")

It does not return the parent itself, and it takes one key at a time. For a subset of parents, add the parents back and join one call per parent with OR:

key in (PAR-1, PAR-2) OR issue in portfolioChildIssuesOf("PAR-1") OR issue in portfolioChildIssuesOf("PAR-2")

Hope that helps.

Welcome!

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

Quick Links

Find more posts tagged with

filter

plan

jql-filter

plan-hierarchy-configuration

jira-roadmap-planning