9 answers
With JQL it's not possible to directly see the date of change, you'll have to open the issue history for each epic and check the date there.
Some alternative solutions:
The second top answer shows how to get status changes with dates using the JIRA REST API: https://community.atlassian.com/t5/Jira-questions/Is-it-possible-to-get-the-issue-history-using-the-REST-API/qaq-p/510094
If you are open to trying add-ons, check out Issue History for Jira developed by my team. You can filter by specific transition like "to Completed status" and create a report like the one below. You will get status transition history for every epic.
Welcome to the community !!
You can use Jira Rest API's and build your own custom solution or if you are open to explore mktplace apps for detailed and flexible reports, take a look at
The app shows the complete history of changes for your filtered issues with the ability to export as well.
Disclaimer - I am part of the app team
Hi @Dominga Savino,
welcome to the community!
an issue's status changes are captured in an issue's issue history, which you can access from the issue view in Jira or via Jira's REST API. Within these status changes, you should find the time stamp that you're looking for - however it can be quite cumbersome to do that by hand.
That's the reason why a lot of users rely on solutions from the Atlassian Marketplace to do that for them. E.g., 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/time of transition to [status], time in [status], time between [status] and [status], and many, many more.
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 Excel or CSV in just two clicks.
Any questions just let me know,
Best,
Hannes
When an issue transitions to "Completed" status, issue resolution date is set by Jira itself. So what you are looking for is the "Resolved" field of the issue. While listing your issues, just add the "Resolved" column into your table report as can be seen on the screenshot below.
If you need more detailed reports on issue transitions, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.
Here is the online demo link, you can see it in action and try without installing the app. To get a report of status transition dates for all statuses, you can have a look at Status Count And Entry Dates report. Entry date(see In Development, Ready for Testing, In Testing, In Development columns.) is status transition date and status count(see #In Development, #Ready for Testing, #In Testing, #In Development columns) is how many times an issue is entered to this status.
App Features:
- This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, resolution time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).
- You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
- Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
- You can set different duration formats.
- You can export reports in CSV file format and open them in MS Excel.
- You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
- You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.
For further details, you can have a look at Status Time Reports How to Videos.
If you are looking for a completely free solution, you can try the limited version Status Time Reports Free.
If you have any questions, feel free to schedule a demo with us.
Hope it helps.
Hello @Dominga Savino
You can use JQL in Jira to find when an epic transitioned to the "Completed" status, but JQL alone does not store historical status changes. However, you have a couple of options:
- Using JQL with Status Change
JQL;
status CHANGED TO "Completed" BY <user> ON <date>- Another Option is Timepiece - Time in Status for Jira developed by my team at OBSS
For a more detailed analysis, Timepiece – Time in Status for Jira provides reports that show exactly when an issue transitioned to a specific status. You can generate a First Transition to Status Date report to see the exact date an epic moved to "Completed."
Here's an example report:
If you'd like to explore this solution further, feel free to check out Timepiece on the Atlassian Marketplace or schedule a demo with us for a walkthrough of the app's features. 🚀
Hope it helps
Ayça
Hi @Dominga Savino ,
- If you have Script Runner, you create a scripted field that will search in the issue history and depict when the epic is transitioned into the desired status.
Then you write a JQL script to retrieve all issues that match your desired value for the created scripted field.
- If you are open to using apps, and you are using cloud, you can use Issue History Dashboard for Jira .
You filter for Issue Type- Epic, Updated Field - status and Value To - Completed.
If by any chance you are using Resolution to determine the completion, you search for Updated Field - Resolution instead.
The example below is using a Story and status but you can use Epic instead.
Regards,
Petru
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.