This feature, as outlined in this ticket's description now exists:

There is a related but distinct feature discussed in some comments here which is tracked on a separate ticket, here: JRACLOUD-18839 Create a JQL functionality to filter the sub-task / child issue for a field value of the parent issue

Although there is a "ScriptRunner Enhanced Search", this is unusable: that plugin periodically runs a query to hard-code the subquery results into a basic query.

It's the periodic / batch nature of the plugin that ensures our query results are outdated, and which makes that plugin unacceptable as a solution.

Like others, I need to be able to find subtasks where the parent meets a specific requirement. In our case, I need to look at open subtasks where the parent item is in a specific fix version. Something like:

status != Done and parent in (fixVersion = 2024Q1) 

I can search items for the fixVersion, but that only shows parent issues, not subtasks. 

This should be included functionality. You shouldn't have to pay for an extension to get the ability to filter by a parent item's setting since in Jira that setting doesn't cascade down to the child item. 

I feel that being able to do some sub-filtering/querying is almost a basic expectation from an "Advanced" query language. I appreciate sub querying adds potential for ridiculous queries but I'd imagine limits on levels of nesting, resultset and given there are plugins that already perform this (provided you stump up more money), Jira should be providing this sort of functionality out of the box.

The alternative is that given devs are moving jobs more fluidly these days (and potentially bringing experiences from other project planning applications in some cases), search for greener grass is inevitable. 

Specifically, I really want to be able to do something like:

Filter all issues in the current sprint where the parent is Done but subtasks are Not Done. 

I would see this could look like:

status != Done
and parent in (
  sprint in openSprints()
  and status = Done
)

I am aware the workflow can be used to avoid the above but consider it a simple example to highlight the need.

We have the same Use case as Bonnie Snipes @bonnie.snipes above, we'd like to filter our Kanban board to only show issues in epics that are in progress. 

As a workaround I'm using automation to add/remove a label to all issues in an epic when the epic changes status... not pretty but it works without extensions.

Need this. We can't use Jira portfolio when tracking Epics with labels. The children stories not getting included. We need the 

Subquery to create the filter required as the source.

Hi, it's possible to perform complex JQL queries in the cloud with JQL Search Extensions and its subqueries functionality. You are able to find links, subtasks, parents and epics of the issues that match the subquery.

For example, after you create a subquery for your JQL "status != OPEN" you can simply search for:

• linkedByQuery="status != OPEN"
• parentOfQuery="status != OPEN"
• etc...

This is very important feature. Atlassian need to prioritized it.

Is there even any point voting for this? Atlassian clearly have no interest in implementing basic features like these when they can cream extra money from the plugins that provide the missing functionality.

Use case

Let me note one use case.

We'd like to query dynamically such as following snippet:

linkedIssue in (issuetype = Epic AND assignee = currentUser())

But not by hard coding IDs:

linkedIssue in (EXAMPLE-1, EXAMPLE-2)