SINCE 3.0
New Field Mapping has two sections. Expose and Receive, similar to Comments and Attachments settings.
- Expose section
The Expose section lets the administrator specify which fields they want to send within the Sync Scheme. Now, the local admin does not make the decision about what the remote admin will map those fields to. They simply send out what they seem appropriate and let the other side decide what they will do with it.
- Receive section
The Receive section has two columns. Local Field and Remote Field. Local Fields are all fields from Issue Types specified in Context within the edited Sync Scheme. Remote Fields are a selection of fields the other side has exposed. It is up to the local admin to decide which field to map and how.
Field Types Compatibility
Field | Support | Map to the same field | Map to Text Field | Map to other fields |
|---|---|---|---|---|
| Project Key | YES | It happens out-of-the-box by Single, shared configuration for many projects configuration. | ||
Issue Key | YES | It happens out-of-the-box.
| YES | |
| Issue Type | YES | YES It happens out-of-the-box by Single, shared configuration for many projects configuration. | YES | |
| Summary | YES | YES required | YES | see Custom Text Field |
| Description | YES | YES | YES | see Custom Text Field |
| Environment | YES | YES | YES | |
| Due date | YES | YES | YES | |
| Labels | YES | YES | YES | Custom Labels Field |
| Priority | YES | YES By name | YES | Custom Select List Field |
| Assignee | YES | YES Based on username | YES | Custom User Picker |
| Reporter | YES | YES Based on username | YES | Custom User Picker |
Version:
| YES | YES By name (with create) | YES | |
| Component | YES | YES By name (with create) | YES | |
| YES | NO These built-in fields are controlled by Jira. Their values can be map only to some other custom fields. | YES |
|
Time Tracking
| YES | YES | YES | |
| Security level | YES | YES | ||
| Resolution | YES | - | ||
| Status | YES | See Workflow Synchronization | YES | |
| Custom field | ||||
| Sprint Field | YES | YES | ||
| Request Type | YES | Atlassian recommends not to change request type but it's available for you | YES | |
| Request Participants | YES | YES Based on username | YES | |
| Text Field | YES | YES | YES |
|
| Number Field | YES | YES | YES | |
| Labels Field | YES | YES | YES | Labels |
| Select List Field | YES | YES | YES | Priority |
| Multi Select List Field | YES | YES | YES | |
| Cascading Field | YES | YES | YES | |
| Checkbox Field | YES | YES By name | YES | |
| Radio Button Field | YES | YES By name | YES | |
| Date Field | YES | YES | YES |
|
| Date Time Field | YES | YES | YES |
|
| Group Picker | YES | YES | YES | |
| Multi Group Picker | YES | YES | YES | |
| User Picker | YES | YES | YES | |
| Multi User Picker | YES | YES | YES | |
| Project Picker | YES | YES By project name It works on same Jira instance but when you synchronize with different Jira instance note that there might not be such a Project | YES |
User fields won't be updated in remote JIRA instance if no user will be found in remote Jira instance.
Backwards compatibility
Because IssueSYNCs aim is to provide integration, we did not want to break any synchronizations between the new 3.0.0 plugin and older versions.
Here are all possible scenarios that we have implemented to maintain bakcwards compatibility, formed as questions:
- Q: I have a connection between two separate Jira instances with pre-3.0.0 IssueSYNC. I want to update one of them to 3.0.0. The second instance will stay on 2.X for now. Will this affect my synchronization?
A: The synchronization will not be affected. The upgrade is done per Connection. The new version will detect the older version and choose to use the old Field Mapping. - Q: I have a Jira instance with pre-3.0.0 IssueSYNC. I only synchronize locally. What will happen to my Field Mappings when I upgrade to 3.0.0?
A: Because all synchronization is done locally, we have full control over the synchronization and there is no remote instance. The upgrade to 3.0.0 will simply convert the old mappings to match the new Field Mapping model. This will not affect the synchronization. Q: I have a connection between two separate Jira instances. They were both using IssueSYNC pre-3.0.0. Both were upgraded to 3.0.0, one after the other. Will they use the new Field Mapping?
A: After both instances have made the IssueSYNC upgrade, they will both still use the old Field Mapping. It is possible however, to upgrade the Field Mapping. This action is available from the configuration screen of any Sync Scheme that works within the upgraded Connection. If both sides have IssueSYNC 3.0.0, a message will appear atop the Sync Scheme summary page. When one of the admins confirms the upgrade, the local and the remote Field Mapping will be converted to the new model automatically. It is best to inform the administrator of the remote instance to inform that an upgrade is going to be executed. The synchronization will not be affected and the new Field Mapping will be available.
Jira Cloud compatibility
Logic and behaviour is same as for IssueSYNC 2.x. The only difference is that Local field alias is no longer present.