Table of Contents
...
In particular, you can expect a different behavior with respect to the following groups of fields:
- Comment
- Attachment
- Summary , and Description and Custom fields
- Component, Affect Version and Fix Version
- Priority, Assignee and Reporter
- Custom Field.
Consider that the synchronization is active on issue creation, editing and linking.
...
Fields mapping around different JIRA field’s type
From | To | Allowed |
|---|---|---|
Summary, Description | Component, Fix/Affect Versions,Assignee, Priority |
|
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 | |
| 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 | |
| Custom fields: Select List (multiple choices), Checkboxes, Select List (single choice), Radio Buttons | Summary, Description, Fix/Affect Versions, Component, Assignee and Reporter | |
...
The mentioned setting is available for mostly of the listed fields available for a field mapping,; the only fields not still allowed to enabled to have this setting are Comments, Attachment Assignee and Reporter.
...
- 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.
...
On issue linking via the Quick actions buttons, all and only the comments added by the user on the linked issue are synced on the source issue.
Anchor Summary
| Summary |
...
Description Summary
| Description | |
| Summary |
...
Description
Summary, Description
| Description |
...
Sync behavior for the fields Summary, Description, Custom fields, Assignee, Reporter is the same for Partnerships configured across the same or different source and destination Url/s.
...
- on issue creation and linking via the Quick actions buttons the issue create screen will not be populated by having the values of the source issue
- on issue creation via the Escalate issue post function the issue will not be populated by having the values of the source issue.
Anchor CustomFields CustomFields
Custom fields
| CustomFields | |
| CustomFields |
Sync behavior for Text Field (single and multi line) is the same for Partnerships configured across the same or different source and destination Url/s .
All other custom field types (select list, radio button, Checkboxes) can be synced only toward a Local Partnership (same source and destination Url).
Depending by the configured sync versus you can expect the syncing behavior described below.
Sync versus is Both
On issue creation via the Quick actions buttons, data are synced from the created issues to the source and, if other synchronizations have been configured on the source issue, syncing is propagated again indefinitely.
On issue creation via the Escalate issue post function, data are synced from the source issue to the target when Sync on create is set to true, syncing is not active on issue creation if Sync on create is set to false.
On linking an existing issue, data are synced from the linked issues to the source and, if other synchronizations have been configured on the source issue, syncing is propagated again indefinitely.
Sync versus is source versus target
On issue creation via the Quick actions buttons, data are synced from the source issue to the created issue.
On issue creation via the Escalate issue post function, data are synced from the source issue to the target when Sync on create is set to true, syncing is not active on issue creation if Sync on create is set to false.
On linking an existing issue, data are synced from the source issue to the created issue and, if other synchronizations have been configured on the linked issue, syncing is propagated again indefinitely.
Sync versus is target versus source
On issue creation via the Quick actions buttons, data are synced from the created issue to the source issue.
On issue creation via the Escalate issue post function, data are not synced.
On linking an existing issue, data are synced from the linked issue to the source issue and, if other synchronizations have been configured on the source issue, syncing is propagated again indefinitely.
| Info |
|---|
In order to allow synchronization working as expected, the field configuration of the target project must include the custom field. Furthermore, the Select List, Radio Buttons and Check-boxes Options must be consistent across the synced source and target fields. If the selected options cannot be synced on the target issue, an alert is logged on the source and on the target issues comments.
|
Issue History updates due to synchronization
...