Filter: Get issues by epic with their subtasks?

[Erik Hennerfors]

Hi

I'm trying to figure out a filter that shows all issues for an Epic but their subtasks is not showing, currently the filter looks like:

issuetype != Epic AND "Epic Link" = GUMK-5 AND project = GuideMaker ORDER BY Rank ASC

Is it possible to get the issues subtest also? Which now does not show

Regards 

[Junio Fernandes]

Due to Why do subtasks disappear when I filter my board using Epic Links, you can't.

In my case I use AM Utils (free add-on) to search all issues and subtasks on it:

A simple example:

issuekey in (issuesSubtasks("'Epic Link' = XXX-99")) ORDER BY Rank ASC

With this I can make boards that swinlanes with stories or projects besides the Epic Link.

[Gary Fitzgerald]

Thanks Junio, Works great!

Can you please explain how you are using this for boards that swimlanes with stories or projects besides the Epic Link?

[Junio Fernandes]

I use this as the filter in the board and configures the board to swinlane by story, projects or epics. If it's not the answer you're looking for, can you be more specific as I can help you more?

[Geert Graat]

Hi,

See this thread: https://answers.atlassian.com/questions/177329 which discusses a lot of options. You will need plugins though, no out of the box solution.

Regards,

Geert

[Daniel Alonso]

Is there any solution for Cloud instances?

[Aida Hota]

Yes there is several

Here is post from Senior Product Manager on https://community.atlassian.com/t5/Jira-Software-questions/JQL-to-show-all-issues-AND-subtasks-in-the-Epic/qaq-p/346433

13 January 2017

Hi everyone,

As part of the migration of Tempo Timesheets to a new technology platform, the tempoEpicIssues() JQL function is either already removed or will be removed soon (depending on whether your instance has a license for Tempo Timesheets).

However, I'm pleased to announce the parentEpic function is now available in JIRA Cloud as a replacement. Searching with parentEpic will return all the issues in the specified epic(s) AND their sub-tasks. The syntax is a little bit different than a standard JQL functions – it's more like searching with a field. So

project = JRA and parentEpic = JRA-123

will return all issues and sub-tasks in the JRA project that are in the JRA-123 epic. The function also supports the != , IN , and NOT IN operators. So you could also search something like

project = JRA and parentEpic in (JRA-123, JRA-456) 

and you will get all issues and sub-tasks in either the JRA-123 or JRA-456 epics.

Refer to the documentation for more information. Happy searching!

Dave Meyer

Senior Product Manager, JIRA

[Deanna Lee]

Hello,

I am trying to create a filter that will pull in all stories, tasks, and subtasks within an epic. I do not have the parentEpic function. (I do, however, have Parent and Parent Link.)

Is there plugin-free workaround to pull in subtasks without the parentEpic function?

Thank you,

Deanna

[Junio Fernandes]

Hope this could help.

((issuetype in (Story, Task, Sub-task) AND issuekey in issuesSubtasks ("'Epic Link' = XXX-99")) OR (issuetype in (Story, Task) AND "Epic Link" = XXX-99))

See my reply to original post. 

[Deanna Lee]

Thanks, Junio. Looks like I need the AM Utils add on for this fix, correct? Unfortunately I'm not able to download this (per my company).

[Junio Fernandes]

Yes! You'll need it. And it's free (thanks cPrime). Your company needs to understand the benefits of acquiring such a plugin that helps their employees, if you're using Server. This plugin doesn't work in the cloud version.

[Shankar Sanjel]

No plugin

"Epic Link" =PROJ-XX OR issue in childIssuesOf("PROJ-XX")

[Denning Coates]

I simply adjusted the JQL on the JIRA filter from Epic Link = JIRA-1234 to parentEpic = JIRA-1234, and this worked for me. 

This is a real game changer for returning more accurate results to include sub task issue types tickets as well as the standard issue type tickets. 

This is especially useful for time tracking.  We have JIRA users that sometimes log their work on sub-tasks associated to the Epic, and for those tickets to populate the "Time Reports" Add on, you must adjust your JQL from Epic Link to parentEpic for any sub-task issues to populate the time report.