Issue Summary

In a Jira Align configuration that is integrated to Jira and uses State Mappings in the Process Flow to match a Jira Align State with more than one Jira Align Process step, then setting the Process Step for a story to the second one configured for a specific state incorrectly sets the first process step instead.

If the same change is attempted against a feature then the correct (second) process step is set

Steps to Reproduce

1. In a Jira integrated configuration use a Jira Workflow that has more statuses than the number of states in Jira Align. 
2. Setup corresponding Process Flows for Stories and Features  in Jira Align and make sure that Paths 1, 3, 4 & 5 in the following article are all configured to match the work/process flows (also make sure that process steps are enabled in the details panel settings for stories and features)  https://community.atlassian.com/t5/Jira-Align-articles/Mapping-States-Steps-and-Statuses-between-Jira-Align-and-Jira/ba-p/1354724 This will result in some JA States being mapped to more than one Jira State and more the one JA Process Step.
3. Create at least one feature and story in Jira (leaving them both in the initial status) and wait for these work items to be created in Jira Align.
4. Use API GET request against the Process Flows (from Step 2) to list the numeric IDs of the process steps for stories and features.
5. Then using the order of the Process Steps, as defined in the process flow for stories, attempt, using a PATCH REST API call, to change the processStepId of a story  to the 2nd step (related to the same JA State)
6. After submitting the patch call, either using a GET call or by refreshing the story in the JA UI, check to see what the process step has been set to.
7. If the story is a child of the feature, then set the story back to the first step in the process flow (as a child story can change the state of a parent feature this is necessary to avoid confusion)
8. Repeat  the same test  (steps 5 to 7) but against the feature
9. Doing a similar test but using the JA UI seems to work correctly for both stories and features. 

In the support reproduction the following mappings were used:

The body of the patch calls contained:

[
  {
    "op": "replace",
    "path": "/processStepId",
    "value": 1228
  },
] 

- there is a bug affecting the story patch calls that means the first time you try this on any specific story you will also need to replace the value of automation with null - see https://jira.atlassian.com/browse/JIRAALIGN-5378 

A demo (from the Atlassian test instance) of using Postman to make PATCH  and GET calls for stories and features, demonstrating that the issue only affects stories has been attached to this ticket.

Expected Results

Both the story and the feature PATCH call to change the processStepId should correctly set the Process Step even when two Process Steps are mapped to the same State.

Actual Results

While the feature sets the correct process step if attempting to set the second process step linked to a state then the first Process Step linked to that same state will be incorrectly set instead 

Workaround

Use the JA UI to change Process Steps