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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Query for status changed doesn't work

Hi all :) ; 

I wrote a query for a next-gen project where I want to check which tickets were rejected in a specified time range. My query looks like this:


project = XYZ AND status changed FROM "Ready for QA" TO "In Progress" BEFORE "2019/08/01" 


My results are always empty but I know there are tickets with this status change. 


Where is my fault?

1 answer

1 vote

I would try using a different Date startOfMonth() and see if you get results. 

I tried to recreate your issue in my own instance and was able to execute without any issues though.

A random side note if you are using Custom statuses....I once ran into a scenario where a Status was failing to return any query results...after fighting it for a bit of time I came to realize that when i built the custom status I had included a space at the end of the Status and because i was not putting the space in the query it was failing to return the actual status i was expecting to see. ex: instead of "In Progress" it was "In Progress "

Thanks for your reply. I tried it out, but it didn't work. I tried the query für another project and it worked, but not for the other one. Maybe the reason could that it's a next-gen project?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events