Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

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

...

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

Image RemovedImage Added

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.

Image Removed

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

Image Removed


Your Jira Cloud connection is configured automatically. 

Image Added


Connecting to Azure DevOps

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

Image Removed

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

Image RemovedImage Added

Synchronization Settings

...

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

Image RemovedImage Added



Type Mapping

Image RemovedImage Added


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

Image RemovedImage Added


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.

Hierarchy Mapping

At the next step you'll be asked to configure hierarchies (Epic link, parent/child link, issue link)

Image AddedImage Added

Field Mapping

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

...

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 ↔ SeverityPriority

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

Image RemovedImage Added

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.

...

You can manually map user accounts in the app:

Image RemovedImage 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 RemovedImage Added


Well done! (smile)