Splitting a Feature does not replicate the ADO area path in the newly created Feature AND creates orphaned stories in ADO

Issue Summary

Splitting a Feature in JA does not replicate the ADO area path in the newly created Feature.
The newly created Feature has no ADO area path.
The newly created Feature retains the ADO ID tag of the original Feature.
So the newly created Feature does not synchronise into ADO
And then on that sync, the child Stories in ADO lose their Parent link and become orphaned.

Steps to Reproduce

In a Program that is synchronised with an Azure DevOps Project

1. In Jira Align Features https://xyz.jiraalign.com/requestgrid
2. Find a Feature with 2 or more Stories
3. At least 1 Story should not be Accepted
4. Open the Feature so that the Details Panel is open
5. Click on "+ Show More"
6. Click on Split
7. Set a new Targeted Program Increment (test was performed with the next PI)
   
8. Click on Split
9. Refresh the screen
10. 
11. Notice that the tags are identical
12. Open the newly created Feature
13. 
14. Notice that the Azure DevOps Area Path is empty
15. Wait for the Work Item Sync Timer
16. Notice that while the original Feature's name has changed to (Split Part 1), the new Feature (Split Part 2) has not appeared in ADO
17. # Notice that the Stories that were moved into the new Feature are now orphaned.

Expected Results

The newly created Feature would have the same Area path as the original Feature
The newly created Feature would not have the original Feature's ADO ID tag.
The newly created Feature would synchronise to ADO
In ADO: The child stories would have a parent link to the newly created Feature.

Actual Results

The newly created Feature has an empty Azure DevOps Area Path field.
The newly created Feature has the original Feature's ADO ID tag.
On the next synchronisation, the child Stories lose their Parent link and become orphaned or misaligned

Workaround

(this assumes that you have bidirectional sync for both Features and Stories configured)

Workaround 1:
Before the Work Item Sync Timer runs.
1. Update the newly created Feature's ADO Area Path and
2. remove the ADO ID Tag "Feature-xx"

Workaround 2:
1. Update the newly created Feature's ADO Area Path
2. Remove the ADO ID Tag "Feature-xx"
Manually update the child Stories in JA with a small change in Description for a successful Story sync.