Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Have you found a cleaner way to filter child issues?

Hello Admins,

I'm looking for advice on guidance on the cleanest way to pull child issues of top level hierarchical issues. The only effective filter query I've found so far that works is: "issue in portfolioChildIssuesOf(ISSUE-X) OR issue in portfolioChildIssuesOf(ISSUE-Y)" & so on repeated another 20 times.

TIA

James

4 comments

The following works for me. 

issuekey in portfolioChildIssuesOf(issuekey/ID goes here)

The filter returns all the child issues below the issue named in the filter.

I beleive this only works if you are using the 'parent link' field that was bundled with advance roadmaps.

Like # people like this
Dave Atlassian Team Apr 01, 2021

Just to follow up on @David Hannon's answer ... the portfolioChildIssuesOf function should do this but it part of Advanced Roadmaps (formerly known as Portfolio) so I believe you will need a Jira Premium license to use this.

Regards,

Dave

Like James Drake likes this

Thank you for your replies, this is the method I've been using. I just wondered if there was a cleaner way of pulling the data. Best, James

Like Dave likes this

I created a somewhat more elaborate way of achieving this using Automation. Let's call the parent issuetype (above the Epic) an "Objective".

I then created a field named Objective and placed it on each screen for Epics, Stories, Bugs, and Tasks. Once the Epics was linked to an Objective (i.e., its Parent Link field linked to an Objective), I copied the Objective issue key to the Objective field.

Then using a bunch of cascading automations, I had the value of Objective copied down to all linked descendants.

This allows me to do a simple jql search for ALL children of any particular objective:

Objective ~[issue key]

This is especially useful when you have parent issues more than one step above the Epic (which we do).

Like James Drake likes this

Comment

Log in or Sign up to comment
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you