Breaking changes

In accordance with the European General Data Protection Regulation (GDPR), Atlassian is introducing changes to Jira Server APIs to improve user privacy. As a Top Vendor for Atlassian Marketplace, ServiceRocket is committed to implementing the changes required in our Connector.

This page explains the upcoming changes to features in version 1.0.0 (General Availability release) onwards of the Connector.

Please contact our support team if you have any further questions.

What's changing?

The changes affect features related to Jira user field types, e.g. Reporter, Assignee or custom user field types.

An affected setup will typically look like this:

Change 1: Value mapping will no longer accept text input

The value mapping screen will now show a dropdown menu to select Jira users. You can search by either username or display name.


This change has already taken effect for any new creation of such mapping.

Potential issue with existing mappings

For existing mappings, you may come across users which have different user keys and usernames. If you have a user who has a different user key and username, you will come across an issue similar to the following:

To resolve this, you will need to delete the value mapping and manually recreate it using the user picker.

Change 2: Related sync will only send user keys

All sync functionality will now only send user keys (instead of Jira usernames) to Salesforce. Refer to both examples below.

If you don’t specify any value mappings, Salesforce will now display the user key:



If you specify a value mapping, Salesforce will display the corresponding mapped value as usual:



Impact on bindings without existing value mappings

If you have a user field type mapping but without any value mapping, all the syncs will now use Jira user keys instead of Jira usernames. This typically affects any Jira user field types e.g. Reporter and Assignee that is mapped to a non-user type field in Salesforce, such as text fields.

Before the changes, the following illustrates the operations:

Jira ( username ) > (Outbound push to) > Salesforce (text field, with value username)

Salesforce (text field, with value username) > (Inbound push to) > Jira (username)

After the changes, it will change to:

Jira (user key) >  (Outbound push to) > Salesforce (text field, with value account ID)

Salesforce (text field, with value account ID ) > (Inbound push to) > Jira (user key)

The above will continue to work despite the usage of user key. However, if you would like to change this behavior to show a more meaningful information in Salesforce, OR making sure an existing association’s inbound push (from Salesforce to Jira) will continue to work, we recommend you to start adding explicit field value mappings.

With explicit value mappings, the operations will be such:

Jira (user key) > (Outbound push to) > Salesforce (text field, with value name )

Salesforce (text field, with value name ) > (Inbound push to) > Jira (user key)

Need help?

We’ve got your back! If you require assistance, contact our support team.