Backbone Issue Sync 5.4.1

November 2022

The Backbone team is pleased to introduce Backbone Issue Sync 5.4.1

This release includes an improvement for the user field mapping as well as the ability to switch a running sync to authentication with Personal Access Tokens.

Fallback user

When syncing users, for example for the reporter and assignee field, the users need to exist on both sides or you need to set up a correlation mapping. In both cases, if a user does not exist Backbone will try to set a fallback user. You are now able to also set this fallback user to "unassigned".  This means that if the user does not exist, Backbone will empty the value of the field.

Switch to Personal Access Tokens

Since Backbone version 5.2.0 you are able to use Personal Access Tokens (PAT) to authenticate with your sync user for new synchronizations. To make it easier, you can now also switch to use PAT in an existing synchronization. To switch, you can go to the synchronization > connection > edit connection and switch the toggle for Personal Access Token. You can then enter the PAT in stead of password for the sync user.

Questions?

Do you have questions or something is not working as expected? Please let us know and create a ticket in our support system or write an email to help@k15t.com.

All updates and fixes in this release