I want to retrieve list of ticket id(Both Parent and Child) based on Custom field value in Parent.

Pramod.Kumar.Ojha

Hi Atlassian team,

I want to retrieve list of ticket id(Both Parent and Child) using JQL query based on Custom field value present in Parent ticket.

Means i have a parent ticket called 'Request'. And in this ticket i have a subtask called 'Instance'.

In Parent ticket i have a custom field 'Customer / Organization' but this is not present in subtask.

I have executed below JQL query and wanted the list which contains both Parent and subtask(child) tickets. But i am getting only Parent tickets.

 

project = "VPC-Intake Cap Demand Mgmt" and resolution is not EMPTY AND type in(Request,Instance) and "Customer / Organization" ~ "ABC"

Please note Request is parent and Instance is Subtask(child).

Please suggest the correct JQL query.
Thanks!

Hannes Obweger - JXL for Jira

Hi @Pramod.Kumar.Ojha

Unfortunately, this is trickier than one might think; as a hierarchical query, it would really require some kind of "join" or "subquery", which isn't available in plain Jira/JQL.

A few directions forward:

• If it's a one-off thing, you could first query the relevant parents, and then use the keys of these parents in a second query, in a "parent in (KEY-1, KEY-2, ...)" clause.

If you want to run your search dynamically, without manually "stitching" two queries together, you'll need extra tooling:

• You might be able to use Jira Automation to "propagate" parent information down to the children, and then use the respective field(s) on the children to include them into your filter. Obviously, this will add a fair bit of complexity to your system.
• There's different apps from the Atlassian Marketplace that can help with that. First, there's a number of apps that extend JQL by additional functions, including hierarchy-related functions. I've used JQL Search Extensions a few times and it works well.
• Alternatively, you could try one of the more hierarchy-focused apps from the Marketplace. These apps typically have their own ways of figuring out parent/child relationships between issues, and provide more powerful ways of searching through issue hierarchies. I myself work on such an app, in which your use case would be easy to solve - I'll provide more details below.

Hope this helps,

Best,

Hannes