---
title: "Change Reason and ResolvedReason during State transition"
canonical: "https://support.appfire.com/space/TSH/1800275482/Change%20Reason%20and%20ResolvedReason%20during%20State%20transition"
format: markdown
---
TFS and Azure DevOps track changes in work items using **revisions**. Whenever any change occurs, a new snapshot of the whole work item is created, and this snapshot contains all the changes that were saved, along with other fields.

All the changes we make before pressing “Save” are saved in one revision. Every time we press the save button, a new revision is created.

Synchronizer does not support changes in `Reason` and `ResolvedReason` that occur outside of state transitions (i.e. those revisions that contain a `State` change).

In order to syncrhonize `Reason` and `ResolvedReason` change them in the same revision as `State` - i.e. when transitioning the work item.

1. Change `State`
2. Change `Reason`
3. Change `ResolvedReason`
4. Press save

This also means that if you will just drag and drop a work item into done column, and change `Reason` / `ResolvedReason` some time later - that will not be synchronized.

> Macro (inline-external-image)

[TFS-3315: As a synchronizer user I would like Synchronizer to pick up changes in Jira Resolution and TFS ResolvedReason that happen outside of state transitions, so that I can easily edit those fields](https://appfire.atlassian.net/browse/TFS-3315)

![image](media://0fc4e32e-7d3e-47b7-a4ce-5e0eaacb31d3)

![image](media://ff0806e4-d910-491b-b658-e4c57e76df3d)