Unfortunately, that is not an option. You might want to check out the plugins in marketplace that lets you write your own export templates.
You can export change histories with the following add-ons:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Better Excel Exporter doesn't yet, but PDF Exporter works on Cloud: https://marketplace.atlassian.com/apps/5167/better-pdf-exporter-for-jira?hosting=cloud&tab=overview
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When will Excel Exporter for cloud being a thing? I feel like people miss it desperately.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Albert Kalytta *sshh* You don't have to wait too long! :) Follow this feature request to be notified of updates.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also, to avoid manual work, you can try Issue History add-on. It lets you get and save all changelogs.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can do it using the Jira Rest API.
Check out Chris Yong's response to this post.
Reproducing it here for easier access:
Jonny, that is fantastic. It works! Many Thanks.
jira = JIRA(options, basic_auth=(USERNAME, PASSWORD)) issue = jira.issue('FOO-100', expand='changelog') changelog = issue.changelog for history in changelog.histories: for item in history.items: if item.field == 'status': print 'Date:' + history.created + ' From:' + item.fromString + ' To:' + item.toString
Gives me:
Date:2012-10-23T09:49:41.197+0100 From:Open To:Queued Date:2012-10-23T09:49:43.838+0100 From:Queued To:In Progress Date:2012-10-23T09:49:45.390+0100 From:In Progress To:Blocked Date:2012-10-29T16:06:36.733+0000 From:Blocked To:In Progress Date:2012-10-31T16:47:40.191+0000 From:In Progress To:Peer Review Date:2012-10-31T16:47:41.783+0000 From:Peer Review To:Customer Approval
Which is exactly what I wanted!
Now I can get data on cycle time, figure out where our bottlenecks are and see which tickets are dropping out of our workflow after we have commited to working on them.
Brilliant.
Many Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check the free plugin Issue History Printer, If you want to deep history of issues.
It was useful for me when I need to get a full change history of issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I open the issue, click on History tab and then right click and print to .pdf. It is high level and works for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are looking to analyze the history, which would be the most common reason to export it, here is a nice Python/Docker tool to analyse some metrics from JIRA, by Martin Aspeli from Deloitte:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In case anyone is interested in the solution for JIRA Cloud, there's now plugin that exports history of changes to JIRA issues - Advanced Export.
Any custom or standard field can be exported with every change as a separate row to make it easy to analyse in spreadsheet or postprocess in any other way.
Here's documentation.
Full disclosure: I'm the author
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Tomasz Kustrzynski.
My company just downloaded the Advanced Export and We are on the free trial. I am having trouble to export Jira Issues and I did not find how to get support for you. Can you help me? Basically I am having trouble when I click on Download the Excel File I have the error: "Failed - Network Failure".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The SQL for JIRA plugin supports it seamlessly. Simply, execute the SQL below:
select * from issuechanges c where c.issueid=10000
it will fetch the full change history for the given issue id (10000 in the example).
Note: the SQL for JIRA plugin provides a pure JDBC driver that you can use to connect remotely to the JIRA API from any JDBC compliant tool (Birt, Jasper Reports, custom Java program, etc) and export data from there in the usual way.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How we can customise the query for scenario given below.
We have to export the list of issues of Project ORR and Issutype RTM, which got changes last week with following information.
1) List of issues, With Issue key
2) What changes done to the field ( Before value and current value)
3) Who made the changes
4) When the changes sone)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.