I want to filter the issues that changed in status during a period (typically last week).
eg. I want to see what issues have transitioned into a certain status in the last week.
For a statuscategory I can do that, using the date in "Statuscategory change date". But I want to have the same for different statuses withtin the statuscategory "open"
Is there anyway in doing that?
just to add to Trudy's great answer: There is indeed no status change date available in Jira, at least not out of the box. If you want to perform a query on (or view) the exact change date/time value, I believe that you'll have to use extra tooling.
E.g., if you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on: JXL for Jira.
JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a long list of so-called history columns that aren’t natively available, including the date of transition from [status] to [status].
This is how it looks in action:
As you can see above, you can easily sort and filter by your history columns, and also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.
Of course, you can also export your data to XSLX (e.g., Excel or Google Sheets) or CSV in just two clicks.
Any questions just let me know,
Best,
Hannes
Hello Hannes,
Your solution look good, but I'm happy with what I can create in Jira. Anyhow thanks for your reply
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @jeroen_wilmes
Yes, that may be possible with the CHANGED operator, using the DURING predicate.
https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CHANGED
status CHANGED DURING("2025/03/03","2025/03/10") and status in (<list of statuses>)
Or it might be possible with the WAS operator.
https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#WAS
status WAS NOT IN (<list of "open" category statuses>) BEFORE "2025/03/03" and
status WAS IN (<list of "open" category statuses>) DURING ("2025/03/03","2025/03/10")
Test these options thoroughly. They may not give the exact results you are seeking.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Trudy, this helps a lot. I was able to create what I want to see.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @jeroen_wilmes
You're welcome.
Could you tell us what your final solution was?
If my responses helped you create your solution, please consider clicking on the Accept Answer button above my responses.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @jeroen_wilmes 👋
If an app from the Atlassian Marketplace is an option for you, i suggest you to try Time In Status. To extract the date of a specific status change from the history
Just simply:
Table view:
Chart view:
Add-on developed by my team.
I hope you find this helpful 🚀
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @jeroen_wilmes
I’d like to introduce you to Timepiece - Time in Status for Jira, developed by my team at OBSS. It is available for both Jira Cloud and Data Center.
If you're looking for a way to track how many times issues have transitioned into specific statuses , Timepiece offers an advanced Status Count Report
Timepiece mainly has several types of time reports (showing how much time each issue spent on each status, assignee, or group) but the app also has Status Count reports.
Status Count Report – Shows how many times each issue has moved into specific statuses.
The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.
Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process.
Hope it helps,
Ayça
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Ayca,
Your solution looks good, but I'm happy with what I can create in Jira. Anyhow thanks for your reply
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.