Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JQL: WAS and WAS IN operators not working

I've run into a puzzling issue with JQL.

This query returns 205 results:

project = "<PROJECT NAME>" AND status = "To Do"

I expect the following query to also give me some results, at least 205 of them:

project = "<PROJECT NAME>" AND status WAS "To Do"

However no issues are returned (same project).

According to this documentation, I had expected this to work:

Find issues that currently have or previously had a status of 'In Progress':

status WAS "In Progress"

Any suggestions welcome!

2 answers

1 vote
Jack Community Leader May 26, 2020

That is odd for sure. It works for me. Can you try different statuses and/or projects?

Hi Jack,

Thanks for your reply.

Thanks for the suggestion to try other projects, as a result I think I've narrowed it down to an issue with next-gen projects (yes, another one!)

This works correctly on every "classic" JIRA project I've tested with. (3 different projects)

This fails as described above on every "next-gen" JIRA project I've tested with. (3 different projects).

Does anyone have access to a next-gen project to confirm my theory?

Jack Community Leader May 26, 2020 • edited

yep....and here is the bug to vote/watch...


and given it is NG and severity is major I expect we will see a fix sometime in 2020.

Like # people like this
John Funk Community Leader May 26, 2020

Nice one, Jack!  

I searched for one earlier and couldn't find it. 

Like Phil likes this

Thanks both for your help today.

Like John Funk likes this
0 votes

Hey Phil - have any moved past the In Progress status?

it works for me, too.

Maybe try was in (To Do) just to see?

Hi John, 

Thanks for your answer.

To be clear, I have not used status was 'In Progress', that's just the example the docs use.

There are still issues with status of To Do, however if I've understood the docs correctly I don't think that should matter:

The "WAS" operator is used to find issues that currently have or previously had the specified value for the specified field.

The WAS IN operator appears to be equally broken for next-gen projects.

John Funk Community Leader May 26, 2020

Hey Phil - I have confirmed that I get the same error with my Next-gen project examples. I will enter a Support Ticket with Atlassian and update back here. 

Like Phil likes this

Thanks for confirming John.

I'm really wishing I'd stuck with classic, next-gen has (so far) been way more trouble than it's worth.

Please let me know when the ticket is raised - I'd like to add my vote and watch.

Hi Guys, any update? about this problem?

John Funk Community Leader Nov 16, 2020

Looks like they are still gathering the impact. 

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,105 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you