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.
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.
I'm looking for a way to basically do something like:
"issues in 'Query1' and status = Cancelled"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So why not do
query1 and status = Cancelled
or
filter=query1filter and status = Cancelled
'issues' seems needless, when the query already returns issues?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you! That was the part I couldn't figure out from our stuff here at work (using "filter" as the starting point).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.