...

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.

...

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

select id, user_key, lower_user_name as lowercase_user_name from app_user where user_key != lower_user_name

...

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

...

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.

...

If you require further assistance, contact the ServiceRocket support team.