JQL to get all issues in an initiative without Portfolio

[Sarah Green]

We use an issue type for Initiative, but we do not have Portfolio. Since we can't add Epics as children of the Initiative, we settle for linking the Epics to the Initiative using the operator "Included in". 

I want to be able to run a query that returns all of the stories for that initiative. I would ideally like to do this WITHOUT simply running a query that lists all the epics (i.e. AND ("Epic Link" = XXX OR "Epic Link" = XXX.....)).

Anyone have insights?

[Ste Wright · Accepted solution]

Hi @Sarah Green 

If it's one Initiative, this should be possible.

Is the operator a link type? I've assumed yes below!

---------------

You can get all the Stories below multiple Epics, based on them being linked to one Initiative.

The JQL you want is:

"Epic Link" in linkedIssues("ABC-1","included in")

In this example, ABC-1 is your Initiative's Key.

---------------

If you want all the issues below multiple Initiatives, you could either use the OR approach - like you did above with Epic Link - or utilise an app from the Marketplace which provides more advanced JQL functions, allowing you to search for a sub-query within your main query.

If you'd like to see that option - let us know and I can provide an example from an app!

Ste

[Sarah Green]

Thanks, Stephen! I couldn't get it to work with "included in" in the query. I removed that bit and it returned the list of issues. 

Any ideas why "included in" didn't work?

[Ste Wright]

Hi @Sarah Green 

You want the link type which displays at an Initiative-level.

I expect (reading it back) that "included in" is actually what is found on Epics to show they're a child of an Initiative, rather than the other way round!

Check what the link type is on your Initiative (the opposite of "included in"). It will show just above the list of child Epics - perhaps it is "includes"?

Let us know if this works :)

Ste

[Sarah Green]

Yes, you guessed correctly. The other operator is "includes" and when using that, the statement worked. Thanks!