Known Limitations
The following list describes known limitations for synchronizing trackers with JIRA:
• Individual trackers in projects that have been imported from JIRA cannot be synchronized. This also applies to tracker of types:
◦ Release
◦ Component
◦ Team
◦ Pull Request
◦ Test Run
◦ Time Recording
• Both synchronization end-points must already exist: Codebeamer tracker and JIRA Project and Issue Type.
• Codebeamer can adjust its own configuration to JIRA's configuration, but not vice versa.
• To configure a JIRA synchronization, the specified JIRA user must be an Administrator of the selected JIRA project. Otherwise, access to the meta data for JIRA issue types is denied.
• To automatically synchronize JIRA workflows, the specified JIRA user must have JIRA System Administration permissions.
A work-around is available for manual workflow synchronization without direct JIRA administration access. see JIRA Workflow synchronization
• Sub-tasks of the selected JIRA issues are not synchronized (imported) to Codebeamer because their issue type is different.
• All items in the Codebeamer tracker are synchronized (exported) to JIRA as a flat issue list. There are no parent/child relationships in JIRA.
• Only the core JIRA User, Group, Version and Component references or pickers are supported. References defined by JIRA plugins and extensions are not supported.
• When no user with the same name already exists in Codebeamer users that are imported from JIRA are initially disabled to avoid exhausting the license pool, and are not made members of the project.
◦ Disabled users cannot be selected in new member field values such as for the Assigned to field Non-project members can also be not selected.
◦ To assign Codebeamer items to imported JIRA users you must activate the user and assing the user to a project role
Activate the user and Assign the user to a project role.
• JIRA Core/Custom fields can be synchronized with the following exceptions:
◦ Labels
◦ Votes
◦ Watchers
 | Due to a known bug  in the JIRA Portfolio's REST API, exporting the Team field changes from Codebeamer to JIRA fails with an Internal Server Error in JIRA.Until this JIRA bug is fixed, the Team field should only be imported but not synchronized (exported). |
• Fields defined by other JIRA plugins and extensions cannot be synchronized unless support is provided for special JIRA custom fields.
• Only the Fieldson the Create Issue screen for the selected JIRA project and issue type can be synchronized.
• Exporting new Codebeamer tracker items to JIRA fails if the JIRA Create Issue screen contains mandatory (custom) fields that are not supported by Codebeamer and that do not have a default value.
• There is a limited conversion between JIRA Wiki Text and Codebeamer Wiki Markup. The following are supported:
and Codebeamer Wiki Markup. The following are supported:◦ Headings
◦ Text Effects: Bold, Italic, Strike-through, Underlined, Superscript, Subscript, Monospaced, Quotes, Text Color
◦ Preformatted Text
◦ Text Breaks
◦ Links
◦ Lists
◦ Images
◦ Tables: Only the basic simple table markup is supported by both systems.
▪ Cells that contain newlines or span multiple lines are not rendered properly in Codebeamer.
▪ Tables defined using the Codebeamer Table Plugin are not rendered at all or are rendered only partially in JIRA.
◦ Any other Advanced JIRA or Codebeamer markup is exchanged as is, and is either not be rendered at all, or is not rendered as expected by the other system. This includes the following
▪ JIRA Attachments, Panels, Code sections, Smileys, etc.
▪ Codebeamer Wiki Plugins, Interwiki Links, etc.
• Only visibility restrictions for comments based on a single role can be synchronized, and only if Rolesare synchronized.
• Codebeamer can only read/import the JIRA Change Log Writing/exporting Codebeamer’s own change history to JIRA is not possible. Only Change Log entries related to mapped Fields are imported.
• Exporting issues from Codebeamer to JIRA is at least 10 times slower than importing issues from JIRA into Codebeamer. This is because each issue comment, attachment, and worklog entry to export requires a separate JIRA REST API request.
• All exported issues, issue changes, attachments, comments and worklog entries are associated with the JIRA user that is used for JIRA synchronization, not with the user, who originally created the issue, issue change, comment, or worklog entry in Codebeamer
• Importing/updating JIRA issues does not trigger any notification or workflow actions on the Codebeamer tracker.
• Removing/deleting issues in Codebeamer or in JIRA is synchronized because Codebeamer tracker items can be removed and possibly restored, but JIRA issues are deleted immediately without the possibility to restore.