| 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.
...
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.
...
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
...
| 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.
...
What is property? - https://developer.atlassian.com/cloud/jira/software/jira-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?
...