Issue Summary

When a Capability Process Flow has more than one step mapped to the Jira Align State "2 - In Progress," the rollup of the state from the child story transitioning to an "In Progress" status in Jira uses the first step created in the process flow, instead of honouring the defined sort order.

Steps to Reproduce

Pre-Requisites

• Have a Program integrated with a Jira Project.
• Have Process Steps for Features and Stories mapped within Jira Statuses (especially for the 'In Progress' process step).

• Have a program with the Capability layer enabled.
• Have a process flow for capabilities with the following creation steps:

• Have a process flow for capabilities with the following creation steps:
  1. Create a step named "First InProgress Step Created."
  2. Create a second step named "Second InProgress Step Created."
  3. Sort the steps so they follow this order:
     1. "Second InProgress Step Created"
     2. "First InProgress Step Created"

Steps:

1. Create a Capability (Capability1) and set the process step corresponding to the state 'Not Started.'
2. Create a Feature (Feature1) under the Capability (Capability1) and set the process step corresponding to the state 'Not Started.'
   (Make sure to set the Jira project for the feature to be created in Jira.)
3. Create a story (Story1) under the feature (Feature1) and set the process step corresponding to the state 'Not Started.'
   (Ensure the Jira project is set for the Story to be created in Jira.)
4. After the Story (Story1) is created in Jira, transition it to the 'In Progress' status or equivalent (based on the mapping defined).
5. Wait for the Jira to Jira Align synchronisation to complete.

Expected Results

'Capability1' is updated to the state: '2 - In Progress' and should reflect the Process Step mapped in the process flow according to the defined order (i.e., "Second InProgress Step Created").

Actual Results

'Capability1' is updated to the state: '2 - In Progress,' but it does not reflect the Process Step mapped in the process flow according to the defined order. Instead, it reflects the first step created (i.e., "First InProgress Step Created").

Workaround

The current workaround is to delete the step created first and recreate it, so it becomes second in the timeline of creation.
CAUTION: All Capabilities associated with the process step that was deleted will need to be updated.