How does Issue History app process data?
- Yuliia Borivets
How does Issue History for Jira app collect data?
The Issue History for Jira add-on aggregates and processes data from the native issue history within Jira.
It works as follows:
All users who change tasks in Jira are recorded in the Jira system logs. Any update you make (status, priority, assignee, or other fields) is a new change that will be added to the system log. The Issue History for Jira add-on can read the full task log "on the fly,” parse the data, format it, and show it to the user.
How does built-in history look? - Single issue only
You can find it when opening each issue under the Activity section.
Issue History for Jira: single & multiple issues changes
With the Issue history for Jira app, you will get a well-structured report for a single issue and a comprehensive report for multiple issues.
Let’s compare how a single issue history with Issue History for Jira looks. The app presents a history of changes for one task with flexible filters and colored highlighting.
Single issue
Issue history for multiple issues
If you need ALL changes on all tasks for a group of colleagues or a project, go for the main add-on window. Here, you can see ALL changes according to your filters (by time, by the user who made the changes, by projects, by JQL requests, etc).
Important: The Issue History for Jira add-on does not store changes in its own database – we parse the selected changes "on the fly".
Restoring deleted issues: How does it work?
The add-on also allows you to return tasks if they have been deleted.
To begin, activate the option to track deleted issues. The app will intercept calls to destroy tasks and save them.
How do we store information about deleted tasks?
All information about deleted tasks is stored in Jira issue properties. This means that the information about the deleted issue is only available on the Jira Cloud in your account and is not stored on the addon's servers.
What is property? - Entity properties
Revert description: How does it work?
The add-on reads the change log in the task and can compare the description BEFORE and AFTER and show the changes to the clients if they want to return. Therefore, you do not need to activate this option. Issue History for Jira reads and formats changes "on the fly.”
What information do we store on our resources?
We can only store configuration information that helps you work with our add-on, such as:
the latest changes to the selected add-on filters
saving reports in the add-on (Save&Load option)
Additional security questions
Check out the section Security & Privacy FAQ page
Contact our support team SaaSJet Support
Haven’t worked with the add-on yet? Give it a try