Child pages
  • Editing a synchronization profile - Cloud Native App

Contents        

You can edit an already existing profile by clicking cog icon and then Configuration link on the Configuration view.

General settings

In the first step, you provide some basic, general profile properties, such as: name, Azure DevOps and Jira locations and credentials.



Configuration fields

Most of the configuration fields are self-explanatory, but some might need a little explanation, which you will find below.

User credentials

User provided in Synchronization Profile needs to have correct permissions in given project. For example, Jira user should have permissions like: Assign Issues, Create Issue, Edit Issue.



Connection testing

Test Connection feature enables you to verify whether TFS4JIRA Synchronizer is able to connect to Jira and TFS / Azure DevOps at specified URL using given credentials. Remember that this option tests only if the connection exists, it doesn't check if given user has correct permissions in project.


Field mappings

Jira issue and Azure DevOps work item are quite a different items. Although both share some common properties and traits, they also differ in many aspects such as default fields sets, workflows and restrictions. TFS4JIRA Synchronizer allows you to configure which issue / work item fields values should be synchronized and how.

A newly created profile comes with an out-of-the box mapping configuration which is a good starting point for further customization.


Field Mappings view

Field Mappings view consists of two sections:

Basic Mappings

Here you will find links to Values Mapping views for some crucial fields/properties, such as: issue type / work item type, issue status / work item state, issue resolution / work item resolved reason. More info about values mapping configuration can be found in the following sections.

Other Mappings

Here you can define additional issue field / work item field pairs that are to be synchronized. In order to define a mapping select Jira field name in the left box and Azure DevOps field name in the right box and click Map button. Previously created mappings can be removed. You can also configure values mappings for a given field mapping by clicking on Values link (see the section below for details).


 Only modifications made to mapped fields will trigger synchronization and only these values will be synchronized. TFS4JIRA Synchronizer ignores modifications made to unmapped fields.


Values Mapping view

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). On Values Mapping view you can configure how should the value be mapped.

The Values Mapping view consists of three sections

Mapping Between

This section contains information about each of the fields in the pair to be mapped, such as name and type.

Mapping mode

Copy values

When Copy values mode is selected, TFS4JIRA 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 many 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.

In order to define a mapping select Jira field value from the left box and TFS field value from the right box and click Map button. A list of already defined mappings is displayed under the boxes. You can remove previously defined pairing by clicking Remove link.

Default value is a value to be set if unmapped value is encountered. 

Mapping direction

You can configure the pair for one-way synchronization (i.e. modifications will be propagated in one direction only) or two-way (modifications at both sides will be propagated).


A new profile is created as disabled, so it won't run automatically. After you've finished configuring the profile, you can enable it on on the Configuration view. There is no limit on the number of created profiles.

  • No labels

This page has no comments.