Help on complex query: ability to return all child issues for a given parent issue

[Paul Alexander]

I read your on-demand plugin policy, and it looks like you do not yet support the Craftforge JQL functions plugin.

https://marketplace.atlassian.com/plugins/org.craftforge.jira.craftforge-jql-functions-plugin

Request: I cannot get default JQL to allow me to write a query that returns all children issues for a given parent issue...I need to be able to get all of the child issues and then use bulk edit to update a couple fields. I only see that JQL can give me all subtasks that belong to a given parent issue, but that is only returned by the Subtasks column and their stringed together.

Reading this post by Tim Baker and the reply by Lingbo, it was suggested to put in a support request:-).

https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+Plugin+Policy

------------------------

Tim Baker

Do any of the supported plug-ins provide the functionality that the Craftforge JQL plugin offers? My team has been using this tool for some really powerful JQL that isn't otherwise possible. We just moved to OnDemand this week, not realizing we'd lose access to this plug-in and are scrambling to gather our metrics without it. Any help that can be provided would be greatly appreciated!

Jul 25, 2012

Lingbo Lu Atlassian Technical Writer

Hi Tim, Sorry to tell you that none of the plugins in OnDemand provides the same functionality. If you need help with this, feel free to open a support ticket at: https://support.atlassian.com/secure/Dashboard.jspa. – Regards, Lingbo

------------------------

[Valentijn Scholten · Accepted solution]

Are you talking about finding all subtasks of a given jira issue?

In that case you can just use parent=<issuekey> in your JQL.

Or do you mean "linked" issues instead of subtasks?

[Paul Alexander]

I just wish I could feed the result of a query into a second query that returns all child issues from that collection of parent issues...that's the dilemma. Yes, I can manually string all of the keys together into a very long query parameter, but that's not a reusable solution.