IssueSYNC 3.0

Owned by Kacper Cygan (Deactivated)
Last updated: Aug 21, 2019 by Marcin Kokoszka (Unlicensed)

With the release of IssueSYNC version 3.0 a major change is coming to Field Mapping. Version 3.0 is backwards compatible with previous versions however, new Field Mapping will only be available between IssueSYNCs with versions 3.0 and above. 

In versions 2.X, in order to map local fields to remote fields, they needed to be explicitly picked on both sides. This means that in order to have the Description field available from a remote instance, the remote instance would also have to map the Description field to some local field. This also meant that when synchronizing field changes, the fields had to be linked together and were set locally from the remote instance. 

The revamped Field Mapping aims to invert this process and let the local administrator decide which fields they want to expose and which fields they want to receive (choosing from fields the other administrator exposed).

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. 

Backwards compatibility

Because IssueSYNCs aim is to provide integration, we did not want to break any synchronizations between the new 3.0 plugin and older versions. 

Here are all possible scenarios that we have implemented to maintain bakcwards compatibility, formed as questions:

  1. Q: I have a connection between two separate Jira instances with pre-3.0 IssueSYNC. I want to update one of them to 3.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. 


  2. Q: I have a Jira instance with pre-3.0 IssueSYNC. I only synchronize locally. What will happen to my Field Mappings when I upgrade to 3.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 will simply convert the old mappings to match the new Field Mapping model. This will not affect the synchronization.


  3. Q: I have a connection between two separate Jira instances. They were both using IssueSYNC pre-3.0. Both were upgraded to 3.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, 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. 


Field Mapping 3.0 with pre-3.0 and Jira Cloud

We have removed Local field alias, so you will see local field and remote field. It will work as before.

*If you have provided local field alias it will still be present in remote Jira instance as Remote field identifier, it's still there behind the scenes. Once you remove and re-add the field you will have to adjust remote configuration also.


Synchronization Scheme

Synchronization scheme can be created only with connection being chosen. You will no longer be able to change connection in synchronization scheme.You will still be able to modify connection itself.