Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Finished updating descriptions and screenshots.

...

You can map links in a similar fashion.
Please note that in case you already mapped the hierarchy at previous step – the used link type will not be available for mapping.


Field Mapping

Image Removed

Field Mapping screen allows you to select which fields should be synchronized between Jira and Azure DevOps.

To configure synchronization options for particular field pair, click ellipsis button – this will take you to the next step.

Info

 Only modifications made to mapped fields will trigger synchronization and only these values will be synchronized. Modificationsmade to unmapped fields will be ignored.

Value Mapping

Image Removed

After TFS4JIRA Synchronizer detects modification in one of the mapped fields, it copies the changed value to linked peer item (be it issue or work item). This screen is a place where you can instruct TFS4JIRA Synchronizer how exactly should the value be transferred.Image Added


Some filed types require additional configuration – value mapping.
In the above example two pairs of fields need additional mapping:

  • Assignee ↔ Assigned To
  • Priority ↔ Severity

To define value mapping - please use the "" button next to each pair (marked in red).


Image Added

Mapping mode

Copy values When Copy values mode is selected , TFS4JIRA the Synchronizer simply copies a modified value attempting to perform type convertion conversion if needed (for example when a numerical field is mapped to string field).  For many For some field types Copy values is the only available mode.

Map values This mode is applicable to dictionary-type fields only. When Map values mode is selected, the values pairing panel appears.

Mapping direction

You can override profile-wide synchronization direction setting and decide that this particular fields pair is to be synchronized in one direction only.

Values mapping

If Map values mode is enabled, you can explicitly defined mapping between allowed fields values on both sides.

Well Done!

Image Removed

Well done! If you're at this step it means that you've successfully created a new synchronization profile. You can now leave the profile disabled or enable it immediately.

Check out tfs4jira - tfs Jira migration product page.

User Mapping

If case both or the systems share Active Directory - user accounts will be automatically.
Otherwise, you can manually map user accounts manually.


Image Added

Enabling the Profile

Before the synchronization takes place – the profile needs to be enabled. This will start synchronization of new changes.
To perform synchronization of historic events – please run initial synchronization after saving the profile.


Image Added


Well done! (smile)