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; } } }

Does Jira Next Gen support history search JQL operators (was, changed, was in, was not, was not in)

john_wang

I was trying to search issues which have been reopened by using the JQL:

"project = "XYZ" and status changed FROM "in review" to "in progress" "

which returned zero result, while I knew there was issues had been reopened.

Based on a previous ticket, "Changed" operator is not supported on Jira cloud

https://community.atlassian.com/t5/Jira-Software-questions/Does-the-JQL-quot-CHANGED-quot-operator-work-in-Cloud/qaq-p/1131454

so I tried to use "was" as suggested

"project = "XYZ" AND status was in ("In Review") and status in ("In Progress")"

And there was still no results returned.

So, does Jira Cloud Next-Gen support any of these history search operators, "was, changed, was in, was not, was not in"? :-(

Accepted answers

Brant Schroeder

John,

Here is a link to cloud JQL operators and how to use them. https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/

Was In, Was Not In, Was Not, Changed, etc. are all operators that work in cloud.

Do you have a any issues that you know meet the criteria of your search. If you are unsure then you should create one to help you ensure that you are getting your syntax correct.

All comments

Brant Schroeder

John,

Here is a link to cloud JQL operators and how to use them. https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/

Was In, Was Not In, Was Not, Changed, etc. are all operators that work in cloud.

Do you have a any issues that you know meet the criteria of your search. If you are unsure then you should create one to help you ensure that you are getting your syntax correct.

john_wang

Hi Brant,

Thank you.

The link you shared is the one I followed to start with, but it was not working, even though I know there are issue which match the query. I am using Jira next-gen, would this make any difference?

John Funk

Hey John,

Did you try to use the JQL with a non-Next-gen project to see if you get results?

Brant Schroeder

I ran a test today and it did not work on any next-gen projects. In my JQL I included an classic and next-gen project. The classic worked but the next-gen did not. I did not see anything in the documentation or on a feature request stating that this would not work for next-gen. You can submit a support ticket to Atlassian to pursue this further as it looks like it should work. https://support.atlassian.com/contact/

john_wang

Hi @Brant Schroeder , thank you for validating it. I thought that might be the case. One more thing adds to the "To Be Aware" list of Next-Gen. I will rename the title.

Interestingly you suggest to submit a Support ticket, because that was my initial intention, but Atlassian triaging process landed me here, maybe that's why you can't find any ticket or feature request.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software