- Synchronization
- Cloud to Cloud
- Local
- Synchronization scope
- Mapping
- Field mapping
- Synchronization history
- Issue view panel
Field mapping
In the table below you can find the list of the custom fields and their available synchronization directions
| Field type on Jira A | Supported directions | Field type on Jira B |
|---|---|---|
| Short text / Single line text | >, <, <> | Single line text |
| Short text / Single line text | > | Multi-line text |
| Short text / Single line text | < | Any other type of field |
| Paragraph / Multi-line text | >, <, <> | Multi-line text |
| Paragraph / Multi-line text | < | Any other type of field |
| Select list (single choice) | >, <, <> | Single select |
| Select list (single choice) | >, <, <> | Radio button |
| Select list (single choice) | >, <, <> | Priority |
| Select list (single choice) | > | Single line text, multi-line text |
| Radio button | >, <, <> | Radio button |
| Radio button | >, <, <> | Priority |
| Radio button | >, <, <> | Select list (single choice) |
| Radio button | > | Single line text, multi-line text |
| Labels | >, <, <> | Label |
| Labels | > | Single line text, multi-line text |
| Select list (cascading) | >, <, <> | Select list (cascading) |
| Select list (cascading) | > | Single line text, multi-line text |
| Select list (multiple choices) | >, <, <> | Select list (multiple choices) |
| Select list (multiple choices) | > | Single line text, multi-line text |
| Checkboxes | >, <, <> | Checkboxes |
| Checkboxes | > | Single line text, multi-line text |
| Date picker | >, <, <> | Date picker |
| Date picker | >, <, <> | Date time picker |
| Date picker | >, <, <> | Due date |
| Date picker | > | Single line text, multi-line text |
| Date time picker | >, <, <> | Date time picker |
| Date time picker | >, <, <> | Due date |
| Date time picker | > | Single line text, multi-line text |
| Due date | >, <, <> | Due date |
| Due date | >, <, <> | Date time picker |
| Due date | >, <, <> | Date picker |
| Due date | > | Single line text, multi-line text |
| Number field | >, <, <> | Number field |
| Number field | > | Single line text, multi-line text |
| User picker (single user) | >, <, <> | User picker (single user). The users are matched based on the account ID. |
| User picker (single user) | > | Single line text, multi-line text |
| User picker (single user) | >, <, <> | User picker (multiple users). The users are matched based on the account ID. |
| User picker (multiple users) | >, <, <> | User picker (multiple users) |
| User picker (multiple users) | > | Single line text, multi-line text |
| Group picker (single group) | >, <, <> | Group picker (single group) |
| Group picker (single group) | > | Single line text, multi-line text |
| Group picker (single group) | >, <, <> | Group picker (multiple groups) |
| Group picker (multiple groups) | >, <, <> | Group picker (multiple groups) |
| Group picker (multiple groups) | > | Single line text, multi-line text |
| URL Field | >, <, <> | URL Field |
| URL Field | > | Single line text, multi-line text |
| Read-only (single line) | >, <, <> | Read-only (single line) |
| Read-only (single line) | >, <, <> | Single line text |
| Read-only (single line) | > | Multi-line text |
| Priority | >, <, <> | Priority |
| Priority | > | Single line text, multi-line text |
| Priority | > | Read-only (single line) |
| Priority | >, <, <> | Radio button |
| Priority | >, <, <> | Select list (single choice) |
| Organizations | >, <, <> | Organizations |
| Organizations | > | Single line text, multi-line text |
| Customer Request Type Custom Field | >, <, <> | Customer Request Type Custom Field |
| Customer Request Type Custom Field | > | Single line text |
Text fields of single-line type do not support markdown, so bolded text, tables, attachments, etc. won’t work. When you are trying to synchronize a multi-line text field to a single line text field, you may receive unexpected results in the form of an unformatted text.
If you choose not to map the Reporter field, it’s value will be automatically populated with Issue Sync’s Technical User.
The Text Field name is variable. By accessing Settings> Issues> Custom fields the configuration of text fields can be found under the following names: Paragraph (supports rich text) and Short text (plain text only).
If a field type or direction of your desire is missing, feel free to let us know about it by raising a support request.
Mapping steps
- Issue Sync Pro chooses either an active or future sprint from the list of sprints to which the issue belongs, but if none match the criteria, it selects the latest closed sprint that matches the requirements.
- After establishing which sprint should be mapped, the app picks the target sprint in the partner Jira.
- The mapping is based on the sprint name. However, when more than one sprint with the same name is found, the mapping is based on status, in order: active, future, and closed.
- If there is more than one sprint with the same name and status, the first one on the list is selected.
You can add a sprint field to a project that doesn’t support it, for example, a Kanban project, if you have administrative permissions. In that case, mapping the sprint field is possible only to the Jira that supports this field type. The mapping in the other direction won’t happen. Also, there wil be no information in the synchronization history either.
Mapping mechanism
Fields available in the mapping configuration are returned from the Create Issue screen.
The fields should be also present on the Edit Issue screen, so the plugin could edit those - otherwise, the fields won’t be updated, and if the mentioned fields are required this may result in a failure during the issue creation.
When mapping to a field with a defined value (Single and Multiselect fields, User pickers, Version, etc):
- The output field should have an option with the same label as the source option, or none if there is none. Character case is being ignored when comparing. In case of multiple same options, the first matching one is selected.
- When creating an issue, and no option could be matched, the default value will be used, and sync will receive Partial Success in result. In case the target field does not have a default option set, Failed status of synchronization will be displayed.
- During update of the issue, and when no option could be matched, the default value of the target field will be ignored, Failed status will be displayed, and the previous field value will remain.
- When mapping a multiselect field to a text field, options are to be separeted by space and a comma.
