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; } } }

Show tasks of Epic in a project in JQL query

Mikk Mihkel Nurges

I'm trying to create a board, which shows Epics of this board along with all tasks under the Epic, even if the tasks might be in other projects.

I've tried something like:

project = ABC OR parentEpic[project] = ABC

But I think I cannot find the correct syntax.

I couldn't find a solution anywhere - is this even possible?

Accepted answers

Hannes Obweger - JXL for Jira

Hi @Mikk Mihkel Nurges

unfortunately, this is a tricky one; as a "hierarchical query", it would really require some kind of "join" or "subquery", which isn't available in "plain" JQL. To the best of my knowledge, you'll need extra tooling for this.

A few directions forward:

You should be able to use Jira Automation to "propagate" an epic's project down to the epic's children, and then use the respective field on the children to include them into your filter.
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 great.
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 to define 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. The downside is that these apps all come with their own views, so you couldn't utilise them in the board view itself, but rather use them as alternatives to the board view.

Hope this helps,

Best,

Hannes

All comments

Hannes Obweger - JXL for Jira

Hi @Mikk Mihkel Nurges

A few directions forward:

You should be able to use Jira Automation to "propagate" an epic's project down to the epic's children, and then use the respective field on the children to include them into your filter.
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 great.
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 to define 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. The downside is that these apps all come with their own views, so you couldn't utilise them in the board view itself, but rather use them as alternatives to the board view.

Hope this helps,

Best,

Hannes

Pasam Venkateshwarrao

Hi @Mikk Mihkel Nurges

As i tried with Structure Addon it is showing tasks under epics.i Hope this will help.

Screenshot 2023-03-24 at 4.50.15 PM.png

Hannes Obweger - JXL for Jira

Just to expand on the last point, this is how this would look in the app that my team and I are working on, JXL for Jira. Put simply, you'd pull in your relevant epics, as well as any potential issues from the other project, enable the default hierarchy (that's just one click), and hide any issues that are outside of your hierarchy (that's another 2 clicks):

Once you have your list of issues, you can work on these directly in JXL (much like you'd do in e.g. Excel or Google Sheets), trigger various operations in Jira, or export them for further processing.

Of course, this view isn't the board - but depending on your use case, you may be able to get your work done here, too.

Any questions just let me know!

Mikk Mihkel Nurges

Thanks! The Automation will not work, because I need the child-tasks to be on different projects. I will start by checking out the JQL extension plugins.

Hannes Obweger - JXL for Jira

The Automation will not work, because I need the child-tasks to be on different projects.

That shouldn't be a blocker though, or am I missing something? I'd imagine a field "Parent epic project" on the children, into which an automation rule would write the epic's current project. So a story itself could be in "PROJ A", and it's "Parent epic project" field could say "PROJ B".