Have you ever searched for when and how Jira tasks have changed? Who has made an update? If you need to see the project’s or a particular user’s changelog for tickets/issues, this post will be helpful.
It’s a well-known fact that the History Tab (built-in solution) gives the ability to monitor the complete information for past activities.
However, this strategy can be complex because it needs a lot of handy monotonous work to analyze several tasks you need data about.
Options you can consider are to export issue history with REST API or other solutions. One of them is Issue History for Jira add-on. It displays the adjustments made to each issue and saves them in a single place. As a result, you’ll have one-stop access to all issues’ updates from the moment of creating to real-time.
Jira users are frequently curious about how they can keep track of their Jira tasks’ status changes. For example, who has moved a ticket between statuses and when. We have created instructions to demonstrate how to get the necessary data.
Go to the column settings menu and select the issue fields you wish to see the changes in. These include:
The report always includes the fields "Issue Key," "Date of change," and "Updated by."
You can choose the “Select issues by” option to filter the list of tasks by project, assignee, or a specific filter. Choose the “Updated by” function and select the assignee you’d want to look at if you want to filter tasks by who has made changes in statuses.
You can track only particular status movements with this capability. For instance, you might be curious about the number of issues that were returned to the assignee to be fixed or improved. The transitions you require must therefore be chosen by clicking on the status column's filter (for example, Under review - Opened):
You can try the Issue History to examine data that can be exported and analyzed using Google Spreadsheets and Pivot Tables.
Follow the steps below:
You now know how to obtain information about the dates and timings of status changes in Jira.
Additionally, to the analysis of status changes, you may look at assignee and priority changes, description or comments, etc. You need to choose another column instead of statuses to accomplish this. Issue History plugin is a place to build different combinations – try to create the report you need.
Yuliia_Borivets__SaaSJet_
1 comment