Add Support for Special JIRA Custom Fields
 |
• Example code shown on or published on GitHub is provided as is.
• PTC Software does not guarantee that any example code will work with current or future Codebeamer versions and specific Jira/Plugin versions
• PTC Software does not provide support for the example code or any @CustomField implementations!
|
Add Support for Special JIRACustom Fields to the JIRA Synchronization
The synchronization of trackers with atlassian JIRA supports only the following:
• JIRA Core/Custom Fields.
• JIRA Agile fields:Sprint and Epic Link.
JIRA custom fields that are defined by JIRA plugins and extensions cannot be synchronized by default, because in the field schema provided by the JIRA REST API, the custom field type is identified by an opaque identifier.
For example, Checklist for Jira:
"customfield_10201": {
"required": false,
"schema": {
"type": "array",
"items": "checklist-item",
"custom": "com.okapya.jira.checklist:checklist",
"customId": 10201
},
"name": "DoD",
"required": false,
"schema": {
"type": "array",
"items": "checklist-item",
"custom": "com.okapya.jira.checklist:checklist",
"customId": 10201
},
"name": "DoD",
In order to do the following you need additional knowledge about each specific custom field, such as Modifying checklists using a REST API:
• Convert JIRA custom field values to appropriate Codebeamer field values and vice versa.
• Convert JIRA custom field changelog entries into appropriate Codebeamer history entries.
Custom Field Extensions
You can add support for specific JIRA custom fields to the JIRA synchronization using the @CustomFieldextension framework.
These extensions are completely annotation based.
Example Code
A fully featured example adding support for Checklist for Jira fields can be found at https://github.com/intland/cb-jira-checklist.