Issue Summary

When the child or grandchild of a Capability/Epic is transitioned to an 'In Progress' state in Azure DevOps (ADO), and the change is rolled up to the Capability/Epic, there is no trace of the state change in the audit log.

Steps to Reproduce

1. Create an Epic/Capability
2. Create a Feature under this Epic/Capability
3. Create a Story under the Feature
4. Make sure that the Story and the Feature are synced to ADO
5. Keep the Story and the Feature with their respective initial states
6. Now transition the Feature or the Story to "In Progress" in ADO
7. Wait for the sync of the state in Jira Align
8. Go back to the Epic/Capability and see that the state has transitioned to In progress
9. Inspect the audit log

Expected Results

There is an entry in the audit stating how the state was moved to 'In progress'
Something like:

  	Update made from Azure DevOps	By External System on <time_stamp>
Capability Updated - State set to 2 - In Progress because Feature ID ZYX state change

or

  	Update made from Azure DevOps	By External System on  <time_stamp>
Capability Updated - State set to 2 - In Progress because Story ID XYZ state change

Actual Results

The is no entry in the audit log corresponding to the change of state by the external system.

Workaround

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