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 not working for status in (Coding) during a period

Cash Coyne_tanpr0

I have this JQL:

project = IM and summary ~ "Model" and status was in (Coding) during ("2023-11-21","2024-02-10")

It returns many issues that were not in a status of "Coding" between those dates. In fact, many were in Coding in 2022!

Any idea what I'm doing wrong here?

Accepted answers

MD_5382aj

Hi @Cash Coyne

I understand your confusion. I'm uncertain about the behavior of "WAS IN," and the response provided by Jira may offer some insight, although I find it challenging to comprehend.

This operator will match the value name (e.g. "Resolved"), which was configured in your system at the time that the field was changed. This operator will also match the value ID associated with that value name too — that is, it will match "4" as well as "Resolved".

https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#WAS-IN

As an alternative - I suggest to use "Changed to" operator:

project = IM and summary ~ "Model" and status CHANGED TO "Coding" during ("2023-11-21","2024-02-10")

Hope it helps

Regards,
M

All comments

Trudy P Claspill

Hello @Cash Coyne

Can you show the full issue history for an issue that is included that you think should not be included?

Is this for a Company Managed project or a Team Managed project?

Uday Kiran Bhaviri_cp1r58

The return issues may not have the current status as 'Coding' but they might have 'Coding' during that period.

And you are searching records from 21 Nov 2023 to 10 Feb 2024. But saying there were many records in 2022. I didn't get that.

Cash Coyne_tanpr0

This is company managed project.

Here is the History of an issue that I don't think should have been retrieved with this JQL:

Cash Coyne_tanpr0

Please see my response to @Trudy P Claspill with a screenshot showing a retrieved issue that was in coding only from 5/19/22 to 5/20/22 which is not in the range I requested.

Bill Sheboy

Hi @Cash Coyne

My understanding is this is a known problem if there are (or have been) team-managed projects used in the site with a status of the same name. The work-around noted in a few open defects is to use the status value's id rather than its name.

https://jira.atlassian.com/browse/JRACLOUD-70797
https://jira.atlassian.com/browse/JRACLOUD-81443
etc.

Kind regards,
Bill

MD_5382aj

Hi @Cash Coyne

I understand your confusion. I'm uncertain about the behavior of "WAS IN," and the response provided by Jira may offer some insight, although I find it challenging to comprehend.

This operator will match the value name (e.g. "Resolved"), which was configured in your system at the time that the field was changed. This operator will also match the value ID associated with that value name too — that is, it will match "4" as well as "Resolved".

https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#WAS-IN

As an alternative - I suggest to use "Changed to" operator:

project = IM and summary ~ "Model" and status CHANGED TO "Coding" during ("2023-11-21","2024-02-10")

Hope it helps

Regards,
M

Cash Coyne_tanpr0

That worked! Thank you @MD !

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jql