Issue Summary

When the child or grandchild of a Capability/Epic is transitioned to an 'In Progress' state in Azure DevOps (ADO), and there is a process flow configured for the parent or grandparent Capability/Epic, the process step is not updated according to its state mapping

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 and process steps
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, but not the relevant process step, causing a mismatch with the state.

Expected Results

The state of the Epic/Capability is updated, and the process step related to the In Progress state is also set.

Actual Results

The state of the Epic/Capability is updated, but the process step related to the In Progress state is not set.

Workaround

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