Synchronize with JIRA
After the configurations are completed on the JIRA Synchronization Setting screen, you can synchronize with JIRA.
The first synchronization is always a full import/export.
Even if automatic synchronization has been configured in regular time intervals, this scheduled synchronization only starts after the first manual synchronization.
Since the initial import/export potentially imports and exports a large number of tracker items, the import and export statistics show only numbers, not the actual item information.
All subsequent synchronizations are incremental imports/exports:
Synchronizing again immediately, or shortly after a previous synchronization typically shows that the synchronization has finished successfully, however, there was no new data to synchronize.
After making relevant changes either in JIRA or Codebeamer, a new synchronization run reflects those changes. Such changes could include
• Changing the Status of an item.
• Changing some attributes, for example Story Points.
• Adding a new Comment and Attachment.
For incremental synchronization runs, detailed information about imported, updated, deleted or failed data is available, as shown in following image:
The configured number of the last X synchronizations can also be viewed at any time later by clicking on the History... link on the JIRA Synchronization window.
Administrators can also look at the synchronization settings that were in effect for each of the synchronizations.
The synchronization history does not store synchronization runs where there was no data to synchronize.
 | Subsequent changes to either the Codebeamer tracker configuration or the remote JIRA configuration such as., new fields, new choice options, workflow changes, and so on have no effect unless the JIRA Synchronization Settings are manually edited and updated. |
A Tracker Synchronization Listener can be implemented and deployed to be notified whenever a tracker is synchronized with JIRA.