Synchronizing Trackers with Atlassian JIRA
Synchronization (Import and/or Export) is available between Codebeamer and Atlassian JIRA on a tracker level.
Prerequisites
• Synchronization requires the JIRA Server REST API (Version 2) and JIRA Server 6.3.8 or later.
• Synchronizing Trackers with Atlassian JIRA Cloud is supported in Codebeamer release 9.4 and later.
 |
If you want to use trackers that were synchronized with JIRA Cloud in Codebeamer 9.3 or earlier with later releases , follow the Migration Steps described in Synchronizing Trackers with Atlassian JIRA Cloud.
|
 |
Synchronization with JIRA Server 9.0 is supported. The Get create issue meta  endpoint of the JIRA REST API V2 has been deprecated in JIRA Server 8.4 REST API, and removed from JIRA Server 9.0 REST API. |
• If you are synchronizing with JIRA Server 9.0 and later:
◦ When the deployment type is Server, and the JIRA version is 8.4 or later, the Get create issue meta project issue types and Get create issue meta fields endpoints must be used.
and Get create issue meta fields endpoints must be used.◦ When the deployment type is Cloud, or the server version is later than 8.4, the old Get create issue meta endpoint must be used.
endpoint must be used.• Both synchronization end-points must already exist:
◦ Codebeamer Tracker Type
◦ JIRA Project and Issue Type.
• Codebeamer can adjust its own configuration to JIRA's configuration, but not vice versa.
There is no restriction on the type of JIRA issue types that can be associated with trackers of a specific type, however, the mappings in the following table can be considered as defaults:
Codebeamer Tracker Type | JIRA Issue Type |
|---|---|
Bug | Bug |
Task | Task |
User Story | Epic or Story |
Requirement | Requirement |
Change Request | New Feature or Improvement |