×

You're using an outdated browser

For a better experience, keep your browser up to date. Check here for the latest version.

Manual

User

Matthias Gaiser

Matthias Gaiser Last update: Jun 26, 2019

Backbone has multiple options for synchronizing user fields (such as assignee and reporter).

The synchronization user needs the 'Assign Issues' permission if you want to map the assignee. If you don't map the assignee, it depends on your Jira configuration if a default assignee will be set or the issue will stay unassigned.

If you want to map the reporter, also the 'Modify Reporter' permission is required. If you don't map the reporter, the sync user will be the reporter of the issue.

Synchronize a user field to the same user

To synchronize the user to the same user in the partner project, select User Passthrough Mapping:

There are three options, depending on how you want to synchronize the field:


  • The User Passthrough Mapping (by username) simply maps the user to a user in the partner instance with the same username.
  • The User Passthrough Mapping (by email) simply maps the user to the partner instance with the same email address.
  • The User Prefix Mapping lets you add or remove prefixes to the start of synchronized user values. This is helpful in cases where your organization has certain naming conventions for internal or external users. E.g. if you add the prefix 'INT-' to synchronized users, the user John Doe in project A would appear as INT-John Doe in project B.

If the same user does not exist in the partner instance, Backbone will throw an error. In order to avoid this, you can set a fallback user – whenever a user does not exist in the partner project, the field will be set to this fallback user instead.

Synchronize specific users to specific users

You can synchronize specific users to other specific users (for example, user 'Tom' in Project A to user 'Thomas' in Project B). To do so, select the User Correlation Mapping setting.

In the User mapping section, click Add Entry to enter the users you want to map. The versions are mapped according to the number they are assigned to – so the version assigned to number 1 on the left side will be synchronized to version 1 on the right side.

You must also select a default user for the field to be mapped to in case you are synchronizing a user that you haven't created a mapping for. You can do this using the Fallback User dropdown. The field value will automatically fall back to this user if the synced user is not mapped.

Synchronize a user field to a text string field

You must map the user field to a text field. The mapping can only be unidirectional, because Backbone doesn't support parsing the user field from the other instance.

In the field mapping configuration, you can enter the text string in the Custom User Format text box:

You can use the following placeholders in the text string:

PlaceholderDescription
${user.displayName}
the user's Jira display name
${user.name}
the user's Jira log-in name
${user.emailAddress}
the email address associated with the user's Jira account

Ignore unassigned

When ignore unassigned is activated, empty user field values are not synchronized. For example: user John Doe is synchronized as an assignee from project A to project B. Activating ignore unassigned means that if John Doe is removed as assignee from project A, project B will ignore this because it is a change to an empty field, and John Doe will remain as the assignee in project B.

Activate the ignore unassigned setting by clicking the Ignore empty values for this user field checkbox:

2x3.9
We use cookies to create a secure and effective browsing experience for our website visitors and to understand how you use our site (i.e. Google Analytics). For more information: click here.
Ok