Table of Contents
...
Furthermore, you must take in consideration that the configured Fields Mappings is already active on issue creation as as on issue editing, exception made for a few set of fields and only on issue creation via the escalate issue post function.
Additionally, the Sync on create parameter allows to set configure for a set of field:
- if the create screen opened via the via Herzum Quick actions button must be pre-populated (Sync on create = True) or not 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 issue.
...
- issue creation and/or linking via Herzum Quick actions
- issue creation and linking via Escalate Issue post functionSync on createparameter setting.
At last, notice that, in general, you can expect the same behavior for a Local Partnerships as for a Remote Partnership.
...
Fields mappings 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 |
|
...
The mentioned setting is available for mostly of the listed fields available for a field mapping, the only fields not still allowed to have this setting are 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.
...