Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,956
Community Members
 
Community Events
176
Community Groups

How to track status changes in Jira?

Status changelog for Jira issues.png

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. 

How to find issue (ticket) history jira.png

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.

Question. When the task went from one status to another (e.g., To Do → In Progress, In Progress → To Review, To Review → Done)? 

Solution 1. Get status changelog in the grid

Go to the column settings menu and select the issue fields you wish to see the changes in. These include:

  • Issue key
  • Status
  • Summary

how to sort issue history fields.png

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.

Issue history filtering.png

Solution 2. Export status changes history

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:

  1. Export data from the Issue History add-on. Choose any field (assignee, comments, etc.) in the Column Manager, including Issue Key, Status, and Summary.

 How to export issue history .png

  1. Open a document using the Google Sheets – Choose a Pivot table function in the Data section.
  2. Order to sort columns: Issue Key- Issue URL – Summary – Date – Status (old) – Status (new) – Updated by.
  3. Exclude a Total one when selecting each column.
  4. Select Status in the Filter section, uncheck Blancs.
  5. You can filter the data at any time by whatever field you want (updated by, issue key, assignee, etc.).

Issue history export.png

Conclusion

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.

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events