JIRA References Synchronization
Before mapping fields of the JIRA Create/Edit issue screens with Codebeamer tracker fields, specify how to handle certain JIRA issue references. These JIRA references are shown in following image:
By default:
• References for User and Group are only imported as user and group names.
• References for Versions and Components are imported as static choice field options.
• References for Teams are imported as static choice field options.
• References for Epic are imported as JIRA Epic keys.
Enable Users import to map the Reporter and Assignees field for JIRA issues to the Owner and Assigned to attributes of the Codebeamer item. You must have the Codebeamer User Admin permission to perform this action.
Keep in mind the following behavior related to Users import:
• If there is no existing Codebeamer user with the same name or email address as a user referenced by imported an imported JIRA issue, a Codebeamer user is created.
• Only the following user attributes are imported:
◦ Username
◦ First/given name
◦ Last/family name
◦ Email address
◦ Avatar/picture
• All imported users are initially disabled because their password cannot be imported and must be manually reset before the user can log into Codebeamer. Also, this avoids exhausting the available number of Codebeamer use licenses.
• Codebeamer tracker items cannot be assigned to disabled users, or to non-project members.
◦ To assign Codebeamer items to imported JIRA users, first activate the imported users, then assign them to roles in the Codebeamer project.
• Because the synchronization is on tracker level, the imported users are not automatically members of the Codebeamer Project.
• Updating a user in JIRA only updates the appropriate Codebeamer user if that user was originally imported from JIRA.
• Deleting a user in JIRA who was previously imported to Codebeamer does not delete that user in Codebeamer. User in Codebeamer cannot be deleted.
• Modifying a user in Codebeamer who was imported from JIRA does not synchronize those changes back to JIRA.
 | The Submitted at and Last Modified at dates of the Codebeamer item also depend on the Users import handling. Import the Submitted at field only if the Submitted by field is imported. |
Enable Versions import to map the Affects Versions / Fix Versions for the JIRA issue to the Detected in and Release attributes of the Codebeamer item, Keep in mind the following behavior related to Versions import:
• JIRA Versions are imported as items of the Releases tracker in the current Codebeamer project.
• Modifications of JIRA Versions (Create, Update or Delete) are synchronized with Codebeamer.
• New Releases added in Codebeamer or modified Releases in Codebeamer that were imported from JIRA, or adding new Releases in Codebeamer are not synchronized back to JIRA, but remain private to Codebeamer.
Enable Components import to refer to JIRA components as Codebeamer config items.
Keep in mind the following behavior related to Components import:
• JIRA Components are imported as items of the Components tracker in the current Codebeamer project.
• Modifications made to JIRA Components (Create, Update or Delete) are synchronized with Codebeamer.
• New Components added in Codebeamer or modified Components that were imported are not synchronized back to JIRA, but remain private to Codebeamer.
Enable Teams import to map the Team field of a JIRA issue to the Teams field of the standard Codebeameritem.
Keep in mind the following behavior related to Teams import:
• Teams import is only available if the JIRA issue type being synchronized has one of the following:
Teams.◦ A custom multiple choice field with the name Team or Teams for which the choice options are the defined teams.
• JIRA Teams are imported as configuration items for the Teams tracker in the current Codebeamer project.
• Modifications of JIRA Teams (Create, Update or Delete) are synchronized to Codebeamer.
• New Teams added in Codebeamer or modified Teams that were imported from JIRA are not synchronized back to JIRA, but remain private to Codebeamer.
Enable Epicslinking to refer to JIRA Epics as Codebeamer work items.
Keep in mind the following behavior related to Epics linking:
• Epics linking can be enabled only if the Epics issue type of the JIRA project is synchronized with an appropriate Epic tracker type in the Codebeamer project.
• Because there is no pre-defined Epic reference field inCodebeamer a new custom target field needs to be defined for the JIRA Epic Link field.