How to export issue history from Jira?

[#1]

Time for monthly/annual reports? Jira’s issue history can give you all the details — what changed, when, and who made the updates. But there’s one problem: Jira doesn’t let you export this data by default. Let’s explore several ways to export issue history — from using the REST API to convenient apps for Jira Cloud, Server, and Data Center.

Every Jira issue keeps a detailed record of its life cycle — from creation to completion. It can be passed from one project to another through different assignees. Every person can change the summary, description, status, labels, or other. All those modifications are saved in the history of the issue. You can find it in the Activity section of every task. (Activity → History tab).

Monitoring of the activity or history records helps to find out:

• What changes have been made
• When modifications occurred
• Who is responsible for updating the issue

Extract issue history using REST API

Jira doesn’t provide history export out-of-the-box, so using REST API is a good option if you don’t mind some programming. Besides, you can use tooltips from the ones who succeed.

Here’s a simple Python example that retrieves the changelog for one issue:

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

You can find more details here.

There is also a great article with a Python example for server users – Extracting complete issue history via API.

The pitfall of this method is that you can extract history only for one issue at a time, not the list of issues.

Export issue history for different hosting types 

Let’s look at what plugins you can use to export the history of issues for Server, Cloud, or Data Center versions.

🟦 Cloud, Data Center

With Issue History by SaaSJet, you can monitor every change made to the selected list of issues. You’ll get one-stop access to all vital data and clear reports to audit your teamwork. 

• Export changes for one or multiple issues in XLSX or CSV

• Schedule automated report export

• Cloud Fortified app (extra security & support)

Check out the sample reports - Excel

Check out the sample reports - PDF

🟦 Data Center, Server

Electronic Signature for Jira by Inlabs helps to comply with CFR Part 11. The add-on requires user authentication so that no one can make changes to the workflow without an electronic signature.

Here, you can export the activity history, which will be automatically attached to issues into PDF format. Also, it tracks and extracts the access attempts. 

🟦 Server

IssuePlus for Jira by Narwhals Consulting allows exporting issue history from one or many issues into CSV or PDF.

If you’re looking for a way to export issue history, consider the ones described in the article. Which method would you like to try?

______________________________________________________________________________________________

FAQs

Can I export full issue history natively in Jira?
No, Jira does not provide a built-in way to export one or multiple items at once. However, you can find apps that allow export to different formats.

Which formats can I export issue history into?
With the right apps or API, you can export history into formats such as CSV, XLSX/Excel, or PDF.

Can I automate or schedule exports of issue history?
No with built-in history. Using Marketplace apps or API solutions, you can create scheduled exports of issue history for reporting or auditing.

[Irene]

Why is the issue log so hard to export?
I'd like to use the export to analyse the flow of our work using GetNave.com, without using the plugin, so I am in control which data is shared with them and compliant with ISO27001. 
I came to the conclusion this is not possible. This seems to me an easy feature for Atlassian. 
Please improve this. 

Here is their instructino 
Loading Your Data to Nave l Nave 

[SergeR]

Print to PDF and "Filter | Export | Print details" should include History block.  Without this I have to manually navigate to each Jira item, scroll down and open History, then take screenshot (after adjusting print scaling).  Repeat for the next 44 samples requested by my SOC2 auditors.

[SergeR]

While I am at it, the Comments block and History block should show date/time/tz for EACH entry.  Need this for 21 CFR Part 11.