-
Sub-task
-
Resolution: Done
-
None
-
None
Hi everyone,
Customers can query on Next-gen epics using the parent =. If you want to combine Epics from both project types, an example of such a query would be:
 "Epic Link" = NPC-6 OR parent = NJDP-5
The Parent field can now be selected as a column in the Global Issue Navigator and exported from Jira.
Regards,


Nathan Sturgess
nsturgess@atlassian.com

Product Manager, JIRA Platform
Original request description
WIth the deploy of the epics and linking the issues to the epics at the Next-Gen projects we can't use the JQL to return issues that are associated to an epic as we can do for classic projects.
Steps to reproduce
- Create a next-gen project
- Create an epic
- Associate multiple issues to the epic
- Go to Issue Navigator and try to perform the search by Epic Link referencing the Next-Gen epic
- No results are displayed
Expected results
Return the list of issues that are linked to the referenced Epic
Actual results
Use parent() function to show the child issues of the Epic. Example:
parent = EPIC-123
- duplicates
-
JRACLOUD-91523 Next-gen Epics can't be used in the Issue search with JQL
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
- Closed
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
[JSWCLOUD-17239] As a user, I'd like to be able to use JQL for Epic Link for Next-Gen project epics
Can you please reopen, as we need Tempo reports to list Project > Epic > Issue > Sub-Task, see problem description here https://community.atlassian.com/t5/Jira-Software-questions/Tempo-report-doesn-t-show-Epics/qaq-p/1597821
Following for need Epic/Parent Name in the query results for macro in confluence. it just shows key which is not helpful. like in JQL results it shows parent name.
I am able to pull the Epic/Parent name in the query but it only exports the Key. Is there not a way to export the name also? I could do this before moving to NextGen.
Hi guys!
It looks like there is no real workaround apart from getting the child issues of the epic and then searching for subtasks of stories in the epic. And this solution only works for some one-off use cases.
If you need full support for Epic->Story->Subtask hierarchies, consider our professional paid indexing service JQL Search Extensions for Jira Cloud.
After you install the app you can get all issues under your epics:
issue in childrenOfIssuesInQueryRecursive("key in (EPIC-1, EPIC-2)")
I hope it's of help to at least some of you!
I have exactly the same problem with sub-tasks and it is driving me slightly mad.
We have now had to ask the team to never log time under sub-tasks, otherwise it is time that just disappears.
Quite frankly the issues with the changes to Epics and parents for next gen projects is baffling.
Hi @Nathan Sturgess,
Above solution works and it pulls only the Story, Task and Bugs under the epic but not the subtasks under the story.
Actually I am trying to use the JQL in Tempo for Logged Time Report. In Classic Software project Filter by Epic works like a charm but since we moved to Next Gen project Filter by Epic is not working. As alternate solution I am trying to use JQL whereas the query appears as below. Problem here is, report pulls all the time logged under Story, Task and Bug issue types but the time logged under "subtasks" are not getting accounted.
JQL: project = ER AND parent in (ER-2)
ER-2 is the Epic
ER-3 - Story 1
ER-4 - Sub Task 1
ER-5 - Sub Task 2
ER-6 - Story 2
ER-7 - Sub Task 1
ER-8 - Sub Task 2
What I am looking for?: My JQL should pull all the Story under Epic "ER-2" along with subtasks so that I can use the JQL in Tempo
Hi karen5,
Sorry for the inconvenience this has caused you, the bug has been triaged to be fixed.
In the meantime there is a workout here: https://jira.atlassian.com/browse/JRACLOUD-74373
Regards,
Nate
Please reopen and add support for timesheet functions.