Skip to main content
Skip table of contents

Sync info panel

Backbone adds a Sync Info Panel to the view issue screen of all issues in your JIRA system, and displays a variety of information on the issue's Backbone synchronizations:

Synced with

The issue key of the partner issue

Issue sync Status

Details about the synchronization status of this issue.

UP TO DATE  All changes have successfully been synchronized

PENDING  You have made changes that have not yet been confirmed as successfully synchronized by the partner instance

ERROR  There is a problem with the synchronization of this issue, and the synchronization has stopped working properly. If you hover over the error message, a tooltip will appear that shows you if the error is in your instance or the partner instance

Synchronization status

Details about the status of the synchronization of this project. For more details, see synchronizations overview.

Last received/sent

The time when the issue last received changes from the partner instance or sent changes to the partner instance

Hide/display the panel 

By default, the Issue Sync Panel is visible to all Jira users – but Jira or project administrators can define which users can see the panel, and who can't.

  • You can enable/disable the Issue Sync Panel on a global level – or for individual projects – by navigating to Project settings > Issue Synchronization and clicking Enable/Disable Issue Sync Panel for all projects.

If you are using Jira Service Management, make sure the synchronization user is member of the Jira-Servicedesk-Group to be able to see the sync info panel


Troubleshooting

  • When someone uses Backbone without assigning project admin permissions to the synchronization user, the synchronization name won't be displayed in the Issue Sync Panel, and the issue won't be linked. There are two ways of fixing this problem.

  • When you are on Backbone version 5.2.0 or higher and the partner instance isn't, this may cause the partner instance to not see the sync info panel information anymore. To fix it, please update both to version 5.2.0 or higher.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.