Table of Contents
...
This guide illustrates what you can expect when the field synchronization has been configured on a mapping.
As first, consider Notice that not all fields defined on your JIRA instances are available for a Field synchronization and not all fields mapping, around different fields, are allowed.After that, consider that depending by the selected field, synchronization.
Following you can find the list of field that can be synchronized and the admissible combinations of synchronizations for different field types.
Furthermore, notice that the syncing behavior can differ for:
...
with respect to the type of field in sync.
E.g. Case of Component, the synchronization is performed on adding a new component same way then deleting a component. Case of Attachment, the synchronization is performed on adding a new attachment exclusively.
In particular, you can expect a different behavior for with respect to the listed following groups of fields fields:
- Comment
- Attachment
- Summary, Description and Custom fields
- Component, Affect Version and Fix Version
- Priority, Assignee and Reporter.
Furthermore, notice Consider that the synchronization is already active on issue creation as on issue editing, exception made for a few set of fields (Comments, Attachment Assignee and Reporter) on issue creation via the escalate issue post functionediting and linking.
Additionally, the Sync on create parameter allows to configure for a set of field option allows chosing:
- if the create screen opened via the via Herzum Quick actions button must be pre-populated (Sync on create = True) or not when when creating an issue via the Herzum Quick actions button
- if the issue created via the Escalate issue post function must be populated based on the value on the Source source issue.
While on issue editing the sync type both is naturally provisioning, on issue creation and/or linking the add-on behavior follows some established conventions that are going to be detailed for:
...
Fields mapping around different field’s type
From | To | Allowed |
|---|---|---|
| Text Field (single line) | Text Field (multi line) |  |
Text Field (multi line) | Text Field (single line) |
|
Summary, Description, Custom fields | Affect/Fix Versions |
|
Summary, Description, Custom fields | Priority |
|
Summary, Description, Custom fields | Assignee |
|
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 | Summary, Description, Custom fields |
|
Fix/Affect Versions | Summary, Description, Custom fields |
|
Assignee | Summary, Description, Custom fields |
|
...
- 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.
...