Advanced Roadmaps roll-up across multiple projects

[Jamie Edmondson]

I have a scenario where I need to see all issues within a particular project in Advanced Roadmaps. That's easy enough. However, in some cases, an Epic in this project may be a child of an issue that is in another project. One solution here is to configure the issue source to only include the issues I need to see from the other project and all of the issues from the original project. But that is tedious. Is there a query that can be written to pull in the parent issue of any given Epic regardless of what project it is in?

Hierarchy:

• Feature (Feature could be on another project)
• --Epic
• ----Story

[Stephen Coleman]

One option would be to use a label in the parent so you don't have to continuously edit the filter, just drop a label on the additional one to include.

(project = ParentProject AND labels in (label-to-include,other-label-to-include)) OR (...)

where ... is the filter you're already using nested within the ( ).

Additionally, if the conditions for what needs to be included are predictable enough, you might be able to add an automation rule to add the label where appropriate.

[Mark Segall]

Hi @Jamie Edmondson - If you're dealing with a small number of features, you could use a filter as issue source like this:

issue in portfolioChildIssuesOf(ABC-123) OR issue in portfolioChildIssuesOf(BCD-234) OR issue in portfolioChildIssuesOf(DEF-345) OR key IN (ABC-123,BCD-234,DEF-345)

Obviously, if you have more than a handful of features, this can get equally tedious to maintain.

Other than that, there are a couple marketplace options out there that can extend JQL to provide something more dynamic.