ADO – Date timestamp of changes in state are not correctly captured - NULL

Issue Summary

When the state of a work item is changed the corrected date timestamp is not being captured
The state in the story changed to In Progress, and checked the tables (or EI) and confirm the timestamp is not captured correctly.
**

Note
This is similar to the known bug to JIRAALIGN-3689: Date timestamp of changes in state is not correctly captured - NULL with Jira and it was fixed on v10.104, but we detected the same bug with ADO at this time.

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Step 1. Create the story and let it sync with ADO
2. Step 2. Change the status to In Progress on one side. Some tests were around going to a different status and back to In Progress.
3. Step 3. Check the tables (or EI) and notice that the timestamp was capture related to that state

Expected Results

Regardless of how the state changes, the timestamp will be captured on the corresponding fields.

Actual Results

Depending on how the state is changed, the timestamp is not captured accordingly.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available