Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
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

JQL query to find child issues of Initiative

Is there a single JQL query which can find all the child issues of a given Initiative? down through the hierarchy including Epics, Issues, etc?

5 answers

1 accepted

4 votes
Answer accepted
Roi Fine Atlassian Team Jan 21, 2018

Hi Traci,

Getting all child issues of an initiative via JQL is possible since Portfolio 2.10, you can check the details here: https://confluence.atlassian.com/jiraportfolio/portfolio-for-jira-2-10-release-notes-940678731.html#PortfolioforJira2.10releasenotes-childissues

Cheers,

Is it possible to use JQL in the Confluence JIRA Issue/Filter macro to display a table of all the issues of a Portfolio Initiative?  The link above seems to be creating a query in Portfolio itself [ issuekey in childIssuesOf("INIT-001") ], but I can't seem to find equivalent JQL syntax that will work in the Confluence macro to retrieve the issues.

I can insert the initiative itself with the macro, and assuming all the issues also have the label "MyLabel", I can generate the table with 'labels = "MyLabel" '.  But I'd like to directly retrieve the initiative's issues.

This is cloud JIRA with Portfolio and Confluence on.

This sound like you can only query for child issues for one Initiative at a time.  Is this correct?  Is there a way you can put more than one Initative in this query issuekey in childIssuesOf("INIT-001")? So, let's say, I want to see all the Child Issues in INIT-100 and INIT-200, can I query for both of them at the same to show on the screen?  Hope this make sense.  Thanks.

Like abhijeetbh likes this

@Mao Lee, childIssuesOf() only takes one argument, but you can do this:

(issuekey in childIssuesOf(INIT-100) OR issuekey in childIssuesOf(INIT-200))

Like # people like this

This hasnt worked for me.  I could be doing it wrong.  I have no idea what Portfolio is.  What I want to be able to do is configure a board and put a fast filter in.  I want the query to return all the Storys from an Initiaive (and the associate epics)  I put 

issuekey in childIssuesOf("INIT-001") in the query box, yet it returns no storys when I click on the filter.   

Any help would be appreciated.

Roi Fine Atlassian Team Jun 05, 2019

Hi Andy, 

 

To make this work you will need to have:

1. Portfolio for Jira Server installed (any version above 2.13)

2. Epics with Parent link assigned to the initiative you are looking for it's children 

3. Stories with Epic link assigned to the linked Epics above

For points 2,3 have a look at this previous post - https://community.atlassian.com/t5/Portfolio-for-Jira-questions/JIRA-Portfolio-epic-link-vs-parent-link/qaq-p/947705

 

I hope this helps,

 

Cheers,

Like # people like this

When will there be support for childIssuesOf() taking in multiple issue keys, or filters as a parameter? I have a filter containing all of the initiatives in my Plan. I'd like a query to return all the children of all those initiatives

Like # people like this

After much trial and error I have been able to create a query that returns all items in the hierarchy using only the initiative id.  

This is with Jira cloud V 7.13 with Scriptrunner but NO Portfolio.  Jira cloud means some scriptrunner functions are not available.

The main difficultly here is to construct a triple nested issueFunction but eventually the right combination of ", \" and ' was found below.  In this example the initiative was XYZ-997 and the Epics have a 'is parent task of' relationship and stories are Epic links.  After the query there is  an explanation of the three sections required.  This has been checked on a single initiative with Epics, stories and subtasks.

(issueFunction in subtasksOf("(issueFunction in linkedIssuesOfAll(\"issueFunction in linkedIssuesOfAll('issuekey = XYZ-997','is parent task of')\"))  AND issuetype not in (Epic)")) OR ((issueFunction in linkedIssuesOfAll("issueFunction in linkedIssuesOfAll('issuekey = XYZ-997','is parent task of')")) AND issuetype not in (initiative)) OR issueFunction in linkedIssuesOf("issuekey = XYZ-997","is parent task of")

Epics :

issueFunction in linkedIssuesOf("issuekey = XYZ-997","is parent task of")   

This piece of the query returns all linked issues to the initiative XYZ-997.  In this case this returns a list of 5 Epics.

 Stories, bugs etc that are linked to the Epics :

((issueFunction in linkedIssuesOfAll("issueFunction in linkedIssuesOfAll('issuekey = XYZ-997','is parent task of')")) AND issuetype not in (initiative))

This nested issue function query takes the list of Epics query above and nests this into a further linkedIssuesOfAll to retrieve all linked issues.  Because the Initiative is also returned, an AND issuetype restriction is used to prevent the initiative appearing in the final results.  Due to the syntax for scriptrunner the quotation marks around the inner query are replaced with '.

Subtasks which are linked to the stories, bugs etc

(issueFunction in subtasksOf("(issueFunction in linkedIssuesOfAll(\"issueFunction in linkedIssuesOfAll('issuekey = XYZ-997','is parent task of')\"))  AND issuetype not in (Epic)"))

This triple nested issueFunction query takes the list of Stories etc, which in turn is derived from the list of Epics and returns all linked subtasks.

Due to the syntax for scriptrunner the escape quotation must be used.  

issuefunction in issuesInEpics("issueFunction in linkedIssuesOfAll('issuekey = XYZ-997','is parent task of')") could also be used to obtain stories, bugs etc that are linked to Epics.

If you use cloud version, https://confluence.atlassian.com/jiraportfoliocloud/searching-for-portfolio-for-jira-custom-fields-in-jql-941619014.html would be useful. 

 

issuekey in childIssuesOf() does not work in cloud version.

Is this still a limitation of the cloud version? 

Like # people like this

Seems to be, yes -- here we are in June 2020 and Cloud doesn't recognize childIssuesOf() as a JQL function. 

Like # people like this

For the Cloud version try this one:

  • issueIsAChildOf in (ABC-123, XYZ-987)
Like # people like this

Parent Link and Childissues of require Jira Portfolio ( which I don't have access to).

I just did "Parent Link" = XXX-0000

This got me everything I need. Think is was using a script runner function in Jira CLoud

I was able to do it with JQL that looked like this 

 

issue = ipe-996 AND project = "IPE Projects" OR issueLink = ipe-996 AND project = "IPE Projects" 

 

That gave me a view that had the parent issues and associated stories only. 

Suggest an answer

Log in or Sign up to answer
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