User

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, and the 'Modify Reporter' permission if you want to map the reporter.

User field mapping options

Passthrough

What does it do?

Synchronizes the user field to the other side.

How do I use it?

Simply select the User Passthrough Mapping, Prefixed User Mapping, or User Passthrough Mapping settings:

  • The User Passthrough Mapping (by username) simply maps the user to a user in the partner instance with the same username. If a user with the same username does not exist in the partner Jira instance, Backbone will throw an error.
  • The User Passthrough Mapping (by email) simply maps the user to the partner instance with the same email address. If a user with the same email address does not exist in the partner Jira instance, Backbone will throw an error.
  • 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. 

Ignore unassigned

What does it do?

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.

How do I use it?

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

Fallback user

What does it do?

If you and your synchronization partner have different userbases in your JIRA systems, sometimes the partner might synchronize user values that do not exist in your JIRA userbase. If you assign a fallback user, the field value will automatically fall back to that user if the synchronized user does not exist in your JIRA userbase.

How do I use it?

You can set a fallback user by selecting the Passthrough Field Value Mapping setting, and typing the user's name in the dropdown list on the bottom-right of the screen.

When the synchronization user has the 'Browse Users' permission, you will also get autocompletion in this select. Please see the global permissions inside your JIRA how you can assign them.

User to String 

What does it do?

The user to string option lets you map a user field to a custom text string.

How do I use it?

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

Cookie Notice

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 Don't track me.