---
title: "TFS4JIRA Self Hosted | Workflow transitions not being synchronized"
canonical: "https://support.appfire.com/space/SUPPORT/663322761/TFS4JIRA%20Self%20Hosted%20%7C%20Workflow%20transitions%20not%20being%20synchronized"
format: markdown
---
## Use Case 

- The customer has configured TFS4JIRA Self Hosted with ticket creation set to Jira → ADO only.
- The sync direction for **issues, work items, comments, attachments, and statuses** is set to **Both Directions** (Jira → ADO and ADO → Jira).
- The customer expects workflow transitions (status changes) to sync bidirectionally in real time after the initial synchronization.
- The customer does not want work items created directly in ADO to automatically generate Jira issues.

## Problem Statement

This workaround resolves a conflict between two requirements:

1. To sync workflow transitions in both directions, set the sync direction to **Both Directions**.
2. However, setting the sync direction to **Both Directions** causes all ADO work items, including those created directly in ADO, to automatically be created as Jira issues.
3. The customer's requirement is that ticket creation should only flow from **Jira → ADO**.
4. The WIQL tag filter (`sync-to-jira`) resolves this by allowing bidirectional status sync while preventing ADO-native work items from creating Jira issues.

## Root Cause

Workflow transitions were not being synchronized because the sync direction for statuses was set to **Jira → ADO only**, while comments and attachments were set to **Both Directions**. For transitions to sync bidirectionally, statuses must also be set to **Both Directions**.

![image](media://33c2bb7d-3b72-4de8-a13c-13c492410f3b)

## Workaround 

1. Change the **Synchronization Direction** from* ***Jira to Azure** to **Both Directions**.
2. Go to **Filter Configuration** and check the box for **Filter Azure items**.
3. Add the WIQL filter: `[System.tags] containing 'sync-to-jira'` to ensure only tagged ADO work items sync back to Jira.

## How It Works

1. When a Jira issue is created and synced to ADO, the label **sync-to-jira** is automatically added to both the Jira issue and the corresponding ADO work item.
2. The WIQL filter ensures that only ADO work items with the **sync-to-jira** tag are synced back to Jira.
3. If a user creates a work item directly in ADO without the **sync-to-jira** tag, that work item will not create a Jira issue.
4. This preserves one-directional ticket creation (Jira → ADO) while enabling bidirectional sync for statuses, comments, and attachments on existing linked items.