TFS4JIRA Cloud Native - Plan Your Synchronization

Owned by Jeff Gleeson
Last updated: Jan 10, 2024
2 min read

For any journey, planning your route can significantly increase your chances of success. With TFS4JIRA Cloud Native, a few preparation steps before configuring a synchronization profile will make the entire process easier, faster, and less prone to error.

Review your Jira and Azure DevOps projects

Confirm administrator access - Configuring TFS4JIRA Cloud Native requires administrator access to Jira and Azure DevOps. If you do not have this level of access, contact a system administrator within your organization for assistance.

Identify the projects for synchronization - Each synchronization profile is between a single Jira project and an Azure DevOps project. Decide on the project you want to synchronize.
Refer to Jira Software projects overview for more information about Jira projects.
Refer to Microsoft’s About projects for more information about Azure DevOps projects.

Review the different aspects of the Projects - In Jira and Azure DevOps, different project types can contain different item and work item types, fields, workflows, and more. It can be helpful to identify the specific components of the project before creating a synchronization profile. Compare the Jira items against the work items and other parts of the Azure DevOps project to identify the components you want to map. Reviewing your projects and identifying what maps to what before you start creating the synchronization profile can make the process faster.

Create an Azure connection

To perform synchronization tasks, TFS4JIRA requires connections to your Jira and Azure DevOps instances. To establish a connection to Azure DevOps, Cloud Native requires an Azure instance URL, synch user email, and an Azure Personal Access Token. Refer to Create a New Azure Connection for instructions.

Create a Personal Access Token

Part of creating a connection to Azure is including a Personal Access Token (PAT). Azure uses a PAT to authenticate into Azure DevOps. The Create a Personal Access Token page has instructions for creating a PAT.

If you use a designated synchronizer account for your synchronizations, use the email for that account when setting up the PAT.

Use a Synchronizer account in Azure DevOps

We recommend setting a designated user in Azure DevOps to act as a synchronizer account rather than a personal account. This allows all issues and work items to be correctly synchronized, regardless of the user who made the changes.

Refer to Add organization users and manage access to learn more about adding a user to Azure DevOps.

 

Once you have finished your planning, you can create a Synchronizer Profile.