Issue Summary

Feature Process Step update because of a Story State change does not honor the Process Flow order if the Process Steps order changed after it was created.

Example:

Consider the 2 Process Steps in a Feature Process Flow, the two are mapped to the Jira Align State "2 - In Progress"
You create the first step named "2 - Created First", then create the second Step named "1 - Created Second". but you configure them in the following order:

• 1 - Created Second <> 2 - Inprogress
• 2 - Created First <> 2 - In Progress

Consider a Feature using this Process Flow, the feature is new and it has a child story.
When the story is moved to in progress, it will update the parent Feature to the first Step created mapped to "2 - In progress", despite it being configured as the second on the order

It will update to 

• 2 - Created First <> 2 - In Progress

When it should update to

• 1 - Created Second <> 2 - Inprogress
•  

Steps to Reproduce

Consider Program Integrated with a Jira Project

1. Create a Feature Process Flow
2. Create the Process Steps to map with the Jira States
3. Configure 2 process steps mapped to the Jira Align state "2 - In Progress"
4. Save
5. Switch the position of the 2 process steps created
6. Create a Feature
7. Create a story under the feature
8. After the Story is integrated with Jira, access it on Jira and move it to the First State of In Progress

Expected Results

The Feature should be updated to Status 2 - In Progress and to the Process Step Mapped in the process flow according to the ordering defined

Actual Results

The Feature is updated to Status 2 - In Progress and to the Process Step that was created first, ignoring the order defined on the process flow

Workaround

Currently, a workaround is to delete the step created first and recreate it again, it will now be second in timeline creation.
CAUTION:

All Programs/Projects integrated using that Process Flow will need to have the recreated Process Step mapped again.

All Features in the process step that was deleted will have the value removed. It will need to force synchronization from Jira so it gets updated