nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can't figure out how to reference another query's output

Heather Hale

I currently have a query to pull stories that is like this:

Query1: issueFunction in issuesInEpics("filter = \"My Project Epics\"")

and another that is like this, to pull cancelled Stories:

Query2: issueFunction in issuesInEpics("filter = \"My Project Epics\"") and status = "Cancelled"

I'm trying to find a way to pull the Stories in Query2 by using Query1 , instead of repeating this part issueFunction in issuesInEpics("filter = \"My Project Epics\"")

I haven't been able to find a way to do this yet (I can only find Portfolio & Epic references.

I cannot hardcode the Epic keys since they are subject to change without me being told about it.

Accepted answers

Radek Dostál

I don't follow what the question is.. You can either specify the JQL inside the subquery, or you can refer to a filter like in your example, but what's the problem?

You can also use ' and \' if you run out of quotes. I think you can chain them too i.e. \\\" but it might take some testing/tries, not quite sure since queries which need quote escapes should usually be broken down to smaller pieces.

All comments

Radek Dostál

I don't follow what the question is.. You can either specify the JQL inside the subquery, or you can refer to a filter like in your example, but what's the problem?

Heather Hale

I'm looking for a way to basically do something like:

"issues in 'Query1' and status = Cancelled"

Radek Dostál

So why not do

query1 and status = Cancelled

filter=query1filter and status = Cancelled

'issues' seems needless, when the query already returns issues?

Heather Hale

Thank you! That was the part I couldn't figure out from our stuff here at work (using "filter" as the starting point).