Contents        

Profiles allow you to synchronize cloud projects between Jira and Azure DevOps.
Each profile syncs one project to another in the opposite platform.

Each profile can have specific settings and filters allowing you to sync only particular items and fields on defined conditions.

Intro

To create a profile, simply log in to your Synchronizer and click "Create Synchronization Profile" button.



You can either create profile manually or start a wizard. Each method has the same options and capabilities.



Make sure to give your profile a descriptive name, so that it's later easy to deduct its purpose.


Connecting to Jira

Start with pasting the link to your Jira.
Make sure you're providing root path to your instance – not to particular project.



Next, please provide Jira authorization credentials.
This account will be used to make all changes to Jira issues during synchronization process.

For Jira Cloud you will need e-mail and API token.
To learn how to generate API token, please see: API Token authentication in Jira Cloud - Cloud Native App



Connecting to Azure DevOps

Similarly, you'll need to connect to your Azure DevOps 
Again, make sure you're providing root path to your instance – not to particular project.



For Azure DevOps Services (in cloud), you will need an e-mail and Personal Access Token of a user account that will perform all synchronization changes.
To learn how to generate API token, please see: Personal Access Token authentication in Microsoft Azure DevOps - Cloud Native App



Synchronization Settings

At this step you'll be able to:

  • select direction of synchronization and
  • particular projects to be synchronized (one for each platform)

You will be able to separately choose sync direction for comments, attachments and links.
Please note that selecting "Not synchronized" will effectively disable synchronization of given elements.



Type Mapping


This screen allows you to select which Jira issue type should be mapped to which Azure DevOps work item type and vice versa.

All unmapped types will default to values selected at the bottom of the screen (Map anything else...).
If you choose "Do nothing" option only items of mapped types will be fetched. This can significantly improve synchronization performance.

State Mapping


You can also map Jira statuses to Azure DevOps states.
Workflows in Jira and Azure DevOps should be as similar as possible, otherwise synchronization could end up in an error.

Field Mapping

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


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).


Mapping mode

Copy values — When Copy values mode is selected the Synchronizer simply copies a modified value attempting to perform type conversion if needed – for example when a numerical field is mapped to string field. 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.

User Mapping

You can manually map user accounts in the app:


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.



Well done! (smile)








  • No labels

This page has no comments.