Scenario

Atlassian has begun taking steps to improve the compliance of Jira Server with GDPR and this potentially affects the configuration of your Classic Connector for Salesforce & Jira.

Each Jira user has multiple properties such username, user key, or email. When you create a new user, the username and user key match. However the username can be modified by admins/users.

Due to the “right to be forgotten”, Atlassian has made changes with regards to usernames and user keys. To comply with GDPR, our Connector will no longer use the username property for synchronization between Jira and Salesforce.

This means that if your configuration uses any user field mapping there may exist mismatches between usernames and user keys, which can cause synchronization issues.

The following table describes how the Connector handles user field synchronization:

Before Classic Server Connector 7.2.0

Moving forward, we will be standardizing how the Connector synchronizes field types between Jira and Salesforce.

After Classic Server Connector 7.2.0

What you can do

To find out whether your Jira instance is affected by the compliance changes, follow these steps.

Step 1

IF you are NOT using any user field mappings, you're good to go and will not need to proceed to the following steps.

IF you are using any user field mappings, then your DB admin will need to run the following SQL query:

Postgres

 This is an example for Postgres DB. You may need to modify this query based on your database environment.

This script queries for any users for which the user key and username are different as a result of creating them after Atlassian applied the compliance changes or simply due to the admin changing the username at any point.

Step 2

IF after running the script, there are no mismatches between username and user key, then you're good to go and will not need to proceed to the following steps.

IF after running the script, mismatches do exist between username and user key, There are two possibilities:

1. If you have mapped values, change the value of the username to match user key from your Jira user management setting. 
   
   

2. If you don’t have mapped values, you have two options:

   1. You have to create a value mapping table. (Jira values == user keys, SF values == usernames). If you go with this approach you have to introduce value mapping for ALL the users that you wish to synchronize to Salesforce.

   2. Change the value of the username to match user key from your Jira user management setting. 
      
      

Manually changing user mappings

• Follow this documentation on how to change the value mappings.

  •  This KB article might also be helpful: How do I synchronize users between Jira and Salesforce?

• Ensure that the Jira values matches the user key and the Salesforce value matches the username for each mismatched record found in Step 2.

Temporary fallback option

If the above procedure is not feasible at the moment, there is a temporary fallback method.

You may toggle the following system property configuration to roll back value mappings to their original behavior. This will require a restart of your Jira instance.

Once the system property has been toggled, the table of affected fields will be reset to as it were before Classic Server Connector 7.2.0:

For more information on setting system properties, consult the Atlassian documentation.

Take note that this method will be removed in a future version of the Connector for Salesforce & Jira.

Need more help?

If you require further assistance, contact the support team.