Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

status changed TO ("A","B","C") returns different results than separate OR clauses — why?

Jim McGowen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 10, 2026

I noticed a discrepancy in result counts when using the CHANGED TO operator with multiple statuses.


These two queries should be logically equivalent but return different numbers of results (65 vs 59):

Concise version (65 results):

status changed TO ("Test", "Done", "Invalid") AFTER startOfWeek() BEFORE endOfWeek()
ORDER BY updated DESC

Verbose version (59 results):

status changed TO "Test" AFTER startOfWeek() BEFORE endOfWeek()
OR status changed TO "Done" AFTER startOfWeek() BEFORE endOfWeek()
OR status changed TO "Invalid" AFTER startOfWeek() BEFORE endOfWeek()
ORDER BY updated DESC

The Atlassian docs state that WAS IN (A, B) is equivalent to WAS "A" OR WAS "B", but that equivalence is only explicitly documented for the WAS operator — not for CHANGED TO. Is the same equivalence supposed to hold for CHANGED TO? If not, what is the semantic difference?

2 answers

3 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 10, 2026

Hi @Jim McGowen 

I recall some older defects describing inconsistent behavior with JQL, changelog-related operators like this, particularly for Team-managed project (TMP) status values. 

The workaround for those cases was to use the id values rather than the status names in the JQL expressions.  Perhaps try that to observe if the results then align.

Kind regards,
Bill

0 votes
John Funk
Community Champion
April 10, 2026

Hi Jim,

Well, that is curious. What is different about those 6? 

Jim McGowen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 14, 2026

Hard to say now. It's next week and they match this week. So, it was something to do with last weeks issues. Can't imagine what. Pretty simple query.

John Funk
Community Champion
April 15, 2026

Sounds like maybe it was a timing issue with your time zone. 

JIm McGowen
April 15, 2026

How so? I used the same functions in both statements: startOfWeek() and endOfWeek(). I should think they always return the same values no matter how they are used.

John Funk
Community Champion
April 17, 2026

Because the start of the week applies to the time zone you are in. Typically it is 8 am or 9 am on a Monday. Some regions of the world are different as they start their work week on Sunday. Also, 8 am in Cairo, Egypt is different than 8 am in Cairo, IL so you would get different results based on that. 

JIm McGowen
April 17, 2026

Ok, but I didn't change timezone between runs of the same query.

John Funk
Community Champion
April 17, 2026

Understood - just saying that it might depend on when you run the query. Is this still happening and a problem for you? 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events