@markbrunwin you should look at this issue.
 

Jason,

How can this be a Severity 3 minor issue? Its fundamental to working with Issue types.

Epics are the classic way of grouping Issues and if you can't run a simple report using epic-link as the JQL search crireria to see your issues, then something is pretty fundamentally wrong.

We have been waiting a year now to get this functionality which I and others reported when Next Gen projects were released. We do not use Next Gen projects now, purely becuase of the lack of this functionality, which is there in standard Jira projects. Please escalate and Fix - it can't be that difficult, if some users are extracting this info from backup files!

Mark

Thanks everyone for voting on this issue. We have another open request for this over on this ticket JSWCLOUD-17239 As a user, I'd like to be able to use JQL for Epic Link for Next-Gen project epics that has more votes. Given it has more weight I'm going to close this ticket and redirect everyone there.

Could I ask that you push your votes over to that ticket and also continue the conversation over there?

Regards,

Jason Wong

Product Manager, Jira Software

This is a dealbreaker for me to use next-gen project. I would love for this to be fixed so that I can start using next-gen.

It was quite nice to go into a Confluence page, insert the Jira macro and enter `"Epic link" = DE-163` and just have them all listed. I hope this is reinstated as well.

Thanks for raising this issue. 

Epics in next-gen work differently to Epics in Classic projects. More information will be forthcoming, but I would like to let you know that we are working on a solution for this.

Regards,

Jason Wong

Product Manager, Jira Software

We have found a slight workaround for reporting. My current Project management and customer have requested extracts or reports on the roadmaps (epics) from the nextgen project. The only place I have been able to locate any linkage data is by extracting the Jira cloud backup. There is a file called entities.xml that has the following lines in it...

<IssueParentAssociationissueId="100XX"parentId="100YY"created="2018-11-17 23:16:28.444241"updated="2018-11-17 23:16:28.444241"/>
By running an extract of these and comparing them against a full list of Jira items from the csv export, I was able to produce a spreadsheet that showed stories to epics and then drop a pivot table on for sorting.
It would be great though for this to be built into the next-gen itself.
 

Same issue here! We are using Jira with the Smartsheet connector and also cannot use the built in "hierarchy" that puts epics above their child issues...I wonder if it is related?? Really holding us up. 

We have the same problem. It's a big problem for us. We aren't unable to filter and show the issues based on "Epic Link". 

I found the same. Epics created within the Roadmap view showed the correct labels and could be linked correctly whereas those created outside of the Roadmap (in my case they have been created in other Classic projects) showed the unlabelled error and could not be linked.