Synchronizing Trackers with Atlassian JIRA Cloud
Synchronizing trackers with Atlassian JIRA Cloud is similar to Synchronizing Trackers with Atlassian JIRA Server.
There are some differences in the JIRA Cloud REST API
to consider:
to consider:• Login using username/password and cookie-based authentication have been deprecated in favor of basic authentication with API tokens. When configuring the JIRA Synchronization Settings for a tracker, where Server is a JIRA Cloud instance (https://instance.atlassian.net), do not enter the username and password of the JIRA Cloud user. Instead use the following:
have been deprecated in favor of basic authentication with API tokens. When configuring the JIRA Synchronization Settings for a tracker, where Server is a JIRA Cloud instance (https://instance.atlassian.net), do not enter the username and password of the JIRA Cloud user. Instead use the following:• User names and keys have been removed from the JIRA© Cloud REST API and replaced with the opaque Atlassian account ID.
and replaced with the opaque Atlassian account ID. |
If you had synchronized trackers with Atlassian JIRA before the username/password login was deprecated, you must perform the following manual migration steps:
• Upgrade to a current Codebeamer release.
• If you had synchronized JIRA Cloud Users to Codebeamer 9.3 or earlier, those users only know their JIRA user name/key, but user names and keys have been removed from the JIRA© Cloud REST API and replaced with the opaque Atlassian account ID.
and replaced with the opaque Atlassian account ID.◦ If you are only importing issues from JIRA Cloud into Codebeamer and user email addresses are available through the JIRA Cloud REST API (depending on Atlassian account privacy settings), Codebeamer can automatically map user references to previously imported users and replace the user's JIRA name/key with the new Atlassian account ID
privacy settings), Codebeamer can automatically map user references to previously imported users and replace the user's JIRA name/key with the new Atlassian account ID◦ If however, you are also exporting issues from Codebeamer to JIRA Cloud, or user email addresses are not available through the JIRA Cloud REST API, the old JIRA user name and key must be replaced with the appropriate Atlassian account ID before the first export/synchronization, otherwise the export/synchronization will fail. For more information see Migrating JIRA User Names/Keys to Atlassian Account ID.
before the first export/synchronization, otherwise the export/synchronization will fail. For more information see Migrating JIRA User Names/Keys to Atlassian Account ID.• For each tracker, that is connected with Atlassian JIRA Cloud (see the Server in System Admin → Connections with External Systems → Atlassian JIRA©), complete the following steps:
a. Click the link in the Connected withcolumn.
b. In the Synchronize with JIRAwindow, click on Settings....
c. Change the Username and Password for the connection as follows:
d. Click 
on the Issues, to see, if access to the associated JIRA Cloud project and issue type works with the new credentials.
on the Issues, to see, if access to the associated JIRA Cloud project and issue type works with the new credentials.e. Adjust the Fields and Links mapping, if necessary.
f. Click OK
g. Run a manual synchronization.