I’m trying to write a JQL query that will help me locate all issues that moved into a specific status after a certain date. Let me explain what I need more clearly.
I want to find all tickets that entered the “Ready for Testing” status after March 15th, 2024. The tricky part is that these tickets might have moved to different statuses since then - some could be closed, others might be back in development, or they could still be in testing.
Basically, I don’t care what status they are in right now. I just need to see every ticket that passed through the “Ready for Testing” status after my target date. The current status of these tickets is not important for my search.
Is there a way to query the status history in JQL to achieve this? I’ve been struggling with the syntax and would appreciate any help or examples.
Oscar64’s got the JQL syntax right, but manually pulling historical data from Jira becomes a pain when you’re doing it regularly or mixing in other filters.
I deal with this all the time tracking deployment cycles. Rather than fighting JQL each time, I set up an automated workflow that grabs the data on schedule and feeds it to our dashboard.
Just create automation that runs your JQL query daily, filters however you want, and sends data where your team actually checks it. Slack, email, spreadsheet - whatever works.
Write the logic once and forget about JQL syntax forever. You can add extra stuff like excluding certain projects or flagging tickets stuck in testing too long.
That’s how I handle all Jira reporting now. Way better than remembering query syntax every few months.
Build something like this in minutes: https://latenode.com
Use the status CHANGED operator with date filtering. Try this JQL: status CHANGED TO "Ready for Testing" AFTER "2024-03-15". This digs through the issue history and grabs any ticket that moved into that status after your date, no matter where it went next. I’ve done this tons of times for workflow tracking and it’s solid. Just double-check your status name matches exactly what’s in your Jira - caps, spaces, everything. Need more precision? Add hours like AFTER "2024-03-15 09:00" but date-only works fine most of the time.
The status CHANGED TO approach works perfectly here. You can combine it with other filters too - like adding AND project IN ("PROJECT1", "PROJECT2") if you only want specific projects. Super helpful when you’re dealing with huge Jira instances that’d otherwise return way too many results. Quick tip: if your org uses custom status names with special characters, wrap them in quotes to avoid syntax errors. Date format should be YYYY-MM-DD like Oscar said, and Jira handles timezones pretty well most of the time.
Heads up - that query can crawl if you’re searching tons of projects. Try adding AND updated >= "2024-03-10" to narrow it down. Issues that transitioned after March 15th probably got updated around then anyway. Really helps on big instances.