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

Advanced Roadmap query to get children issues at each level of the hierarchy

We just migrated to Jira Cloud and we previously had a filter query in Server that provided all the child relationships at each level of the hierarchy:





The scriptrunner function that made this possible is no longer supported. How can I achieve this in the cloud environment? We want to be able to see all related items whether they are directly or indirectly related to the other filter criteria. In the Server version, the items not directly meeting the strict filter criteria, would show up greyed out.

1 answer

1 vote

I am not sure if I follow what you are trying to achieve...

Could you post a screenshot that explains it a bit more or tell us what script runner function you used on the server version?


This will get the children of all the Initiatives and their descendants regardless of what project they are located, from Initiative down to subtasks. We manage the size of the query return by adding additional field filters.  The  issueFunction scriptrunner function portfolioChildrenOf and portfolioParentOf does not exist in the Cloud instance and the issuesInEpics does not function the same way as it did in Server

This should be the standard view for you.

Just make sure you include all the data you want in issue sources.

I only get the Initiative and Epics but not Stories and Sub-tasks because the fields we are filtering on are only at the Init and Epic level. The scriptrunner functions pulled in the related descendants at the story and task so I'm looking for a way to create the view I share in my previous post (that view is from our Server instance)

Like Alyssa Jones likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events