Issue History – How It's Handled

All Jira work items contain a history tab that displays all changes made to that work item .

This article explains how the work item history is handled when work items are synchronized using Backbone.

Default Behavior

The work item history tab is not a field in Jira – so it is not synchronized between Jira instances like fields are. Instead, the work item history is automatically created and updated locally in each Jira instance as changes are made to the work item there.

This means that the work item history behaves in the following ways:

• If you synchronize a project with work items that already have an issue history, the existing history will not appear in the newly created synchronized work items

• If multiple changes are made to a field within a single synchronization interval, then the multiple changes will be reported as a single edit in the synchronized work item

• All edits synchronized from the other Jira instance will be recorded as being made by the synchronization user

Synchronize to a Text Field

If you want to preserve the history information from the other side, you can also create a field mapping from history to a multiline text field of your choice. This way, Backbone writes the a textual representation of the history into the field.