nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Query to find all issues related to an EPIC (including subtasks)

Tobias Lindell (EXT)

This seems to be one of the most ridiculous problems I have ever encountered. How can it even be hard (let alone impossible) to find all issues related to a specific EPIC without making the ugliest query ever?!

In order to find the epic issue (including its subtasks) along with its epic linked issues and their respective subtasks, I seem to have two alternatives:

Alternative 1

issue = PROJ-1234 OR parent = PROJ-1234 OR "Epic Link" = PROJ-1234 OR issueFunction in subtasksOf("\"Epic Link\"=PROJ-1234")

Alternative 2 (which sucks since this query will also return issues that are linked using other link types)

issue = PROJ-1234 OR issueFunction in linkedIssuesOfAllRecursiveLimited("issue = PROJ-1234", 2)

I have gone through every forum thread imaginable and I don't understand why for example "parentEpic" or tempoEpicIssues() doesn't work. I think the former is not available for JIRA server and the latter you need developer permissions for.

Accepted answers

All comments

Ignacio Pulgar

You're right: The parentEpic() function is just on Cloud.

Your Alternative 1 query is almost correct, and it can be slightly improved like this:

key = PROJ-1234 OR "Epic Link" = PROJ-1234 OR issueFunction in subtasksOf("\"Epic Link\"=PROJ-1234")

Alternatively, you may save a filter named 'Epic' with this jql:

"Epic Link" = PROJ-1234

...so that you can use it in a nicer query like:

key = PROJ-1234 OR filter = Epic OR issueFunction in subtasksOf("filter = Epic")

Tobias Lindell (EXT)

Hi Ignacio,

How is "key" different from "issue"? It returns the same result, right?

Kindly,

Tobias

Ignacio Pulgar

Yup, it's the same than issue but shorter, which is specially good for long queries... hehe.

Ethan Kim_yntmyy

Thanks!

Jason Vogel_u25alh

Using JIRA v7.7.0 - no addins...

Type this into Advanced Search

issue = BIT-1230 OR parent = BIT-1230 OR "Epic Link" = BIT-1230 OR issueFunction in subtasksOf("\"Epic Link\"=BIT-1230")

Received this response...

Field 'issueFunction' does not exist or you do not have permission to view it.

What am I missing?

Ignacio Pulgar

You need to count with ScriptRunner addon installed in your Jira instance for being able to use issueFunction.

Jason Vogel_u25alh

Is there a way to do this without having a plugin installed?

Ignacio Pulgar

Hi Jason. I'm afraid there's no JQL way in Jira Server to get the subtasks of issues that belong to the specified epic without the help of a plugin.

Of course, there would be ways for getting them through SQL, by querying directly against the database, but that's usually considered a bad practice...

Fabian Hußl

Thanks!

Deepa_y250m2

This is what worked for me example:
(project = DF149 AND "Epic Link" = DF149-2496 AND (issuetype = Story OR issuetype = Task )) Or (project = DF149 AND issueFunction in subtasksOf("\"Epic Link\"=DF149-2496")) Order by "Start date"

Eduardo Godinez

JQL Query	Purpose
"Parent Link" = JIRA-123 AND issuetype = Task AND resolution = unresolved	It displays any open task within an epic
parent in (JIRA-123) AND resolution = unresolved	It displays any open subtask within an epic
"Parent Link" = JIRA-123 AND issuetype = story AND resolution = unresolved	It displays any open story within an epic

This is what I use

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

atl-gruland