\uD83E\uDD14 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 issuetypes.
\uD83C\uDF31 Solution
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 workitems 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 initial-syncronization and live-synchronization.
Filters: When enabled, it is important to always 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.
Unmapped issuetypes: In case there are unmapped issuetypes 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.