I wish to track how issue statuses evolve within a JIRA project over time. Currently, I have a query that returns only one record per item, but I need additional details. Specifically, I’d like to see the date when each status update occurred along with the previous status and the new status. My goal is to enhance my tracking process to capture these extra details for better reporting. For instance, a revised query might be:
sprint = 'AlphaRelease' AND status UPDATED AFTER '2024-03-01'
Any advice on refining this approach would be welcome.
In my experience, I’ve encountered similar challenges while trying to thoroughly monitor status changes in JIRA. The standard JQL doesn’t permit retrieving detailed historical information, so I had to look into alternative approaches. I found that using add-ons like ScriptRunner really expanded my options, as they allow the use of functions that expose changelog details directly in your queries. Otherwise, I had to resort to the JIRA REST API to fetch the complete change history, then parse the response to extract dates and transition details. This approach, although more technical, provided a comprehensive view of the status evolution.
Based on my experience, if you require advanced tracking beyond what JQL offers, consider leveraging automation to extract detailed status history. I set up a process that calls the JIRA REST API periodically, storing all status update events into a database for flexible querying. This method provides the additional perspective of capturing both the previous and current statuses along with precise timestamps. Although it introduces a bit of setup overhead, the benefit of customizable reporting and the ability to integrate data with other tools greatly improved our tracking efficiency.
hey, i ended up using the jira rest-api to record every transistion by a custom script that logs each update. works well for me if you can do a bit of code tweaking, might just be what you need.
Through my experience, I discovered that leveraging business intelligence tools like eazyBI can offer a robust alternative to the approaches I see mentioned here. When I needed to monitor status transitions beyond what JQL allowed, I imported comprehensive changelog data directly into eazyBI. This tool enabled me to build detailed reports that included exact timestamps, previous statuses, and the new statuses after transitions, without the need for intensive scripting. The visual dashboards not only simplified tracking but also provided a dynamic analysis capability over recurring intervals, making reporting more efficient.
My approach involved using JIRA’s automation rules to capture and log status transition details. I set up an automation trigger that fires on issue updates, specifically when the status field changes. This rule then records the previous and new status along with the timestamp into a custom field or sends the data to an external system for further analysis. The setup is moderately complex but offers real-time data capturing without additional third-party tools. This method has worked well in environments where external add-ons are not permitted, providing flexibility and comprehensive tracking.