Issue History for Jira

The built-in Jira functionality allows you to see the history of changes on the single issue level.

To get the history of issue: Open the issue → Scroll down to the Activity section → Choose the History option.

Built-in functionality has no options for creating the issue history report. That’s why we’ve launched the Issue History for Jira. It allows you to organize the activity history for multiple issues according to your needs.

To create the issue history report:

• Filter issues by Project, Sprint, Label, etc.
• Select the date range.
• Add custom and standard fields to the grid.

Jira’s Audit Log captures key system events, including issue deletions.

How to use it:

• Go to Jira Settings > System > Audit Log.

• Use filters or search for keywords like “issue deleted.”

Jira has no option to restore deleted issues, tickets, or other work items. So, you can try to track and recover all your deletes with Issue History for Jira. Read about the Restore deleted issues feature.

We don’t store any customer data in our infrastructure excluding hashed customer id and add-on configs. Everything is processed interactively and displayed to end-users. We use application internal logs, but without customer-related data, include only details about requests performance/status/error code.

Issue History for Jira helps to meet such Part 11 FDA requirements:

• get an audit trail (log of all changes made to a file or data) to prevent falsified records
• track and keep deleted Jira issues to be sure nothing is lost forever
• export data from the system into a clear document (XLSX or CSV) to present it to FDA inspection

*There is no option for electronic signature in the plugin.

Our mission is to ensure information system uptime, data integrity, availability, and business continuity. We have process-level plans for recovering critical technology platforms and the telecommunications infrastructure in case of disaster. Learn more

Jira issue change history includes all the updates that have been made to a single issue/ticket. That covers status, description, priority, sprint, assignee, and other issue fields updates. You will find out when the changes were made and by whom.

For example, Assignee Name changed the Status 5 days ago from In Progress to Done.

There is no option to export issue history from Jira without plugins or REST API. With Issue History by SaaSJet, you can extract any work item history as XLSX or CSV files with two clicks. Additionally, you can schedule an auto-export and send a report to the designated parties at your preferred time.

Deleting issues in Jira is a powerful action and permissions work differently depending on your project type.

For company-managed projects:

1. Go to Jira Settings > Issues > Permission Schemes.

2. Find your project’s scheme and click Permissions.

3. Under Issue Permissions, locate Delete Issues.

4. Click Edit (or Add if missing).

5. Assign it to a role or group (e.g., Project Role: Administrators).

6. Save your changes.

Now choose an issue, you can find the Delete option while clicking on the three dots icon.

More here: How to delete & store deleted issues in Jira

According to Jira pricing, we’re unable to manage the price relative to the number of actual users. Atlassian offers discounts for the annual subscription, so you can pay less in that way.

Backup/Recovery files are required to return systems to a state where they contain the information and data that was resident on the system shortly prior to the disaster.

Backup tape locations and retention periods are summarized in the table below:

1. The plugin is Cloud Fortified, so it ensures additional security, reliability, and support.
2. The app is part of the Marketplace Bug Bounty Program. Learn more
3. SaaSJet company has completed the Security Self-Assessment Program. Learn more
4. SaaSJet is SOC 2 Type 2 compliant.