Table of Contents
...
While on issue editing the sync type both is naturally provisioning, on issue creation and/or linking the add-on app behavior follows some established conventions that are going to be detailed for:
...
Fields mapping around different Jira field’s type
From | To | Allowed |
|---|---|---|
Summary, Description | Component, Fix/Affect Versions,Assignee, Reporter |
|
Priority | Summary, Description, Custom fields |
|
Component | Fix/Affect Versions |
|
Fix/Affect Versions | Component |
|
| Fix Versions | Affect Versions |  |
| Affect Versions | Fix Versions | |
Assignee | Reporter |
|
Reporter | Assignee |
|
Component, Fix/Affect Versions,Assignee | Summary, Description |
|
Fields mapping around different custom field’s type
From | To | Allowed |
|---|---|---|
| Mapping between different custom field types | ||
| Text Field (single line) | Text Field (multi line) | |
Text Field (multi line) | Text Field (single line) |
|
| Select List (single choice) | Radio Buttons | |
| Radio Buttons | Select List (single choice) | |
| Select List (multiple choices) | Checkboxes | |
| Checkboxes | Select List (multiple choices) | |
| Select List (single choice), Radio Buttons | Select List (multiple choices), Checkboxes |  |
| Select List (multiple choices), Checkboxes | Select List (single choice), Radio Buttons | |
| Select List (multiple choices), Checkboxes, Select List (single choice), Radio Buttons | Select List (cascading) | |
| Select List (cascading) | Select List (multiple choices), Checkboxes, Select List (single choice), Radio Buttons | |
| Mapping between custom fields and Jira default fields | ||
Custom fields (Text Field) | Priority |
|
Priority | Custom fields(Text Field) |
|
| Summary, Description, Fix/Affect Versions, Component | Custom fields: Select List (multiple choices), Checkboxes, Select List (single choice), Radio Buttons, Select List (cascading) | |
| Custom fields: Select List (multiple choices), Checkboxes, Select List (single choice), Radio Buttons, Select List (cascading) - | Summary, Description, Fix/Affect Versions, Component, Assignee and Reporter | |
...
Notice that the comments added by the user, that are candidates to be synced, are managed by the add-onapp, so that they can be associated to the synced comment created by the system, by following the following convention:
- a comment added by the user includes the following header: Comment synced by HQL (id:<Issue id>)
- a comment added by the system includes the following header: Comment synced by HQL (<Partnership Id>: <Issue id>)
Notice that sync behavior is the same for Partnerships configured across the same or different source and destination Url/s.
...
Notice that when sync fails as default the add-on app set to Null the value of the target field. An exception is made for field configured to be required where the existing value is retained.
...