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

Any way to bring back all stories and sub-tasks under an Initiative+Epic parent in a filter?

Mat Pemble (Adm)

In setting the issue scope for a Portfolio plan I want to use a filter that shows all issues linked to an Initiative. With the standard heirarchy:

Intitiative -> Epic -> Story -> Sub-task

I have Epics split across multiple projects but can't find a simple way to just set a filter to include all levels of issues connected to an initiative. The best I can do is bring back all the linked Epics via JQL parentLink field, but the stories and sub-tasks are not pulled in.

Ideally I don't want to have to rely on users ensure that each new story is tagged with a custom component that I can add to the filter.

Am I missing a simple and easy way to achieve this?

Thanks!

Accepted answers

All comments

Mat Pemble (Adm)

Luckily I already have ScriptRunner installed so was able to achieve what I wanted with:

"Parent Link" = PROJECT-17 OR issueFunction in issuesInEpics("'Parent Link' = PROJECT-17")

It still excludes sub-tasks but we don't really use that level of detail within Portfolio.

Maree Milne

Hey Mat

We're having issues with the schedule section not working if our filters include the "issuesInEpics" jql function - would you mind letting me know which versions of Portfolio and ScriptRunner you are using?

Cheers

Maree

Mat Pemble (Adm)

Hi Maree,

Yes, unfortunately we have run into the same issue now that we have completed our high level estimates. All the epics and stories display fine in the scope panel and we can create new stories via this screen without problems, but none of the issues are picked up for scheduling.

We will probably have to kludge it by creating a cross project component which is actually the project name. Definiteley not ideal and not a neat approach.

I intend to raise it as a bug, but as it's connected with use of a 3rd party add-in I don't expect much.

Cheers,

Mat

Maree Milne

Hey Mat

Bugger, was hoping it was just my version combination

I've raised a support request with Atlassian for the issue, will respond again if it gets anywhere

Cheers

Maree

Mat Pemble (Adm)

Hi Maree,

Just had a notice from Atlassian support indicating that there was a bug in the Scriptrunner plugin:

https://productsupport.adaptavist.com/browse/SRJIRA-2314 https://productsupport.adaptavist.com/browse/SRJIRA-2313

which is fixed on the latest version of the plugin 5.0.14. release note - https://scriptrunner.adaptavist.com/latest/jira/releases/current-release.html

I have upgraded to the latest version of ScriptRunner and am pleased to say that this does indeed fix the problem and issues are now being picked up and scheduled as expected in Portfolio!

Hope that helps.

Cheers,

Mat

Dave Coop

Why not simply use the search query of: "Parent Link" in linkedIssues("<insert Initiative ticket ID>")

Debbie_lrs42o

That query does not include sub-tasks

Welcome!

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

Quick Links

Find more posts tagged with

jira

advanced-roadmaps