Creating Jira filter for Q2 roadmap but can't include "is caused by" topics

[Nika Mamporia]

Hi, trying to set up a filter for advanced roadmap app for my project and we need to include customer tickets which are linked to Epics for customer clarity when we share the project roadmap for Q2 and any future ones, using this JQL query "project = "Project name" AND "Potential Delivery Target[Dropdown]" = "Q2 2022" AND issuetype = Epic" lists all Epics planned for Q2 but can't get the tickets that are linked with these epics as causes to show here. Any solutions apart from getting a different app, solutions I found require to purchase another app to expand JQL.

Thanks

[Jack Brickey · Accepted solution]

So are you trying to find specific issues in the epic with a link type of "is caused by" or are you simply trying to find all issues in the epic? If you are trying to find the issues in the epic you don't want to use issuetype = epic.

a couple of possibilities here...

project = "Project name" AND "Potential Delivery Target[Dropdown]" = "Q2 2022" AND "Epic link" in (epic1, epic3, epic22...)

or...

project = "Project name" AND "Potential Delivery Target[Dropdown]" = "Q2 2022" AND "Epic link" in (epic1, epic3, epic22...) And issuelinktype = "is caused by"

[Nika Mamporia]

I'm trying to filter out Epics and associated issues with type "is caused by" so need to display both Epic and any issues that are linked within those epics. 

[Jack Brickey]

By "type" is this a link type? Are the epics linked to other issues? Note - I am not using advanced roadmap so I may be misguided here. Still trying to understand your situation. Maybe a screenshot of your issue where the "is caused by" is referenced would assist.

[Nika Mamporia]

Yes, the issues are linked within the Epic as caused by.  So, for customer roadmaps we need to include the Epic and linked issue that is marked as "is caused by" as that's their ticket ID which they can track, this way we can give the customer a way to track their issues without having to come to us to explain what specific Epic might be in regards to their request, bug, etc.

[Jack Brickey]

Unless there is something in common between the epic and the underlying stories you can't construct a JQL OOTB for this. One possible idea would be to add a label to all of these issues using automation. For example you could trigger on the issue being updated and if it has a link of is caused by end it has an associated epic then you could branch on that epic and add a label to it. Once you get this working you could do a JQL something like below...

project = "Project name" AND "Potential Delivery Target[Dropdown]" = "Q2 2022" AND (issuelinktype = "is caused by" OR labels = is-caused-by)

Get exactly what you want but hopefully this gives you something to ponder incoming up with a workable solution.