| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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.
...
| Info |
|---|
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.
How does it work?
To begin, activate the option to track deleted issues. The app will intercept calls to destroy tasks and save them.
...
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.”
| Info |
|---|
WE DO NOT SAVE changes to the Description field on our resources because the change log is stored precisely on Jira Atlassian's properties. |
...
What information do we store on our resources?
...