...
In the first step, you provide some basic, general profile properties, such as: name, Azure DevOps and Jira locations and credentials.
- Profile name
- Jira's project name
- Azure DevOps (ADO) URL, synchronizer user credentials, organization and project.
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 ADO user provided in Synchronization Profile needs to have correct permissions in sufficient privileges for a given project. For example, Jira user should have permissions like: Assign Issues, Create Issue, Edit Issue.
Connection testing
A 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 existscan be established, it doesn't check if given user has correct sufficient permissions in for the project.
| Anchor | ||||
|---|---|---|---|---|
|
...
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.
...
In order to define a mapping select Jira field value from the left box and TFS Azure DevOps field value from the right box and click a Map button. A list of already defined mappings is displayed under the boxes. You can remove previously defined pairing by clicking Remove link.
...