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

JQL: WAS and WAS IN operators not working

Phil_ckuhn7

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!

Accepted answers

Jack Brickey

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

All comments

Jack Brickey

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

John Funk

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

it works for me, too.

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

Phil_ckuhn7

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.

Phil_ckuhn7

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?

Phil_ckuhn7

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

John Funk

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.

Jack Brickey

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

JRACLOUD-72180

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

John Funk

Nice one, Jack!

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

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

jql