Note: Please note! The change history item cannot be updated on the Jira Cloud side. Exalate allows sending change history info from Jira Cloud to other instances but not updating it on the Jira Cloud instance.
Exalate allows syncing change history between Jira On-premise instances or sending over the change history info from the Jira Cloud instance. Issue change history is a list of change history items. The change history item includes several records, such as the person who made the change; the time at which the change was made; the new and old values of the field that was changed.
issue.changeHistory is an array of ChangeHistory.
| Object | ChangeHistory |
| Fields |
|
| Introduced in | 1.0 |
Fields
|
# |
Field name |
Comment |
Object type |
|---|---|---|---|
| 1 | id |
|
Long |
| 2 | Author |
|
User |
| 3 | created | The creation timestamp | Date |
| 4 | changeItems |
|
Array of changeItems |
Please use the scripts below to synchronize the change history.
Source Side
JIRA ON-PREMISE JIRA CLOUD
Outgoing sync
replica.changeHistory = issue.changeHistory
Destination Side
JIRA ON-PREMISE
Incoming sync
issue.changeHistory = replica.changeHistory
Note: If you want to keep the change history filed up-to-date for Jira Cloud, you can try to sync the change history item into a text field. Check out How to sync change history to the text custom field.