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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

What is the easiest way to extract transition history of multiple issues in a excel or CSV?

In our company, we're dealing with a use case, where we need to extract in an excel or CSV and use transition history of multiple issues in a project in the below format 

  • Issue Key
  • Issue Summary
  • Status Changed From
  • Status Changed To
  • Status Changed on Date/Time

Please advise if this can be queried/exported directly somehow, or if there is an add-on for this purpose?

4 answers

3 accepted

1 vote
Answer accepted

Hello @soumya wadhwa ,

Jira does not provide this information as a report from its user interface.

If you can do custom development, you can use Jira REST API to get this data, one issue at a time.

Since you are on Jira server, you can also query this data directly from Jira database.


I don't know how you plan to use this data but our team at OBSS built Time in Status app that includes many different reports based on it. It is quite probable that you will be developing something similar.

Time in Status by OBSS is available for Jira Server, Cloud and Data Center.

Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well as entry/exit dates for all statuses. You can also combine statuses into consolidated columns to see metrics like Ticket Age, Cycle TimeLead Time, etc. You can calculate averages and sums of those durations and counts grouped by issue fields you select. (For example see the total InProgress time per Epic, or average Cycle Time per issuetype). 

tisCloud_StatusDuration_Report.png  tisCloud_IssueView_Chart_StackedColumn.png  tisCloud_MainPage_Chart_Pie_ExcludeMarked.png

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.

The app has Custom calendar support which means you can get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)

Finally, the app has History Trim feature. This feature allows you to report on a subsection of issue histories instead of the whole history. Very useful when you want to focus on changes made during sprint or project phase.

If you need to integrate this data into another systemi Time in Status by OBSS also provides a REST API which can give you all the reports you can get from the UI.

Using Time in Status you can:

  • See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
  • Calculate averages and sums of those durations grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
  • Export your data as XLS, XLSX or CSV.
  • Access data via REST API. (for integrations)
  • Visualize data with various chart types.
  • See Time in Status reports on Jira Dashboard gadgets (released for cloud, server&DC gadget coming soon)


1 vote
Answer accepted

Better Excel Exporter 


This will enable you a complete "Change log" on issues. All your Issue history will be exported using this tool.

Which also enable Worklogs exporting  and Agile reports also.

Thanks, will check it out

Thanks It helped.


As an alternative, you can try out our plugin

Agile Tools : Epic Tree & Time in Status 

We have this exact report which you need as shown in screen below. Also the app provides 5 important features, for roll ups of time estimates and story points, along with time tracking of issues and users.

  • Time in Status :- More than 7 types of Time in Status reports to track your issues.
  • Worklogs & Time tracking Report :- Track time spent by resources with multiple filters / category / grouping features
  • Timesheet :- View/Enter your time spent for multiple days
  • Links Hierarchy :- View/Manage roll up for hierarchy (up to 10 levels), based on your Issue Links parent child relationship.
  • Epic Hierarchy :- View/Manage roll up for standard Jira hierarchy. Epic -> User Story -> Subtask


TIS- Status Transition Dates.PNG

0 votes
Answer accepted

Hi @soumya wadhwa ,

We built Status Time app for this exact need. It provides reports on how much time spent in each status as well as status entry dates and status transition count. Report can be exported as CSV, so that you can use external tools like Microsoft Excel or Google Spreadsheet to process the exported data.

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. It has various other reports like assignee time, status entry dates, average/sum reports(eg. average in progress time per project).

Here is the online demo link, you can see it in action and try. Hope it helps.

Hello @soumya wadhwa 

You can try Time between Statuses (server version) add-on to extract those data.

This add-on helps to calculate the time between statuses and shows when an issue has moved from one status to another.


I hope, you find it helpful

Best regards, Mariana

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you