Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

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?


5 answers

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

That query does not include sub-tasks

Hi Maree,

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

which is fixed on the latest version of the plugin 5.0.14. release note -

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.



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.



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



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?



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.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events