TFS4JIRA Cloud Native | Items don't sync from AzureDevOps to Jira Cloud

Owned by Adriana Hernandez, created
Last updated: Mar 06, 2024 by Gabriela Costa
1 min read

 Problem

When items are not synchronizing from Azure DevOps to Jira and the logs don’t show any errors, it might be related to the synchronizer user, filters, or unmapped issue types.

 Solution

  1. The synchronizer user: According to the TFS4JIRA Cloud Native documentation, the synchronizer user needs to be a dedicated user account that doesn’t interact with work items because changes made by this user will be skipped. → Check if the Azure DevOps user added in the connection tab is the one making the changes expected to sync.

This applies for both initial synchronization and live synchronization.

  • Filters: When enabled, it is important always to check filters and understand what is being filtered out; anything that doesn’t match the filter will be skipped, and these actions won’t be visible in the logs. → Check if the filters are filtering out the changes expected to sync.

  • Unmapped issue types: If there are unmapped issue types and there isn't a default value set, this can also prevent issues of a specific unmapped type, not syncing. → To avoid this issue, identify which item types are not being synchronized and double-check the types mapping in TFS4JIRA.