Issue Summary

Asset fields are grouped together in the created request, not matching the form order

Steps to Reproduce

1. Configure a request type with a mixed order of Asset and non-Asset fields. Have more than 2 Assets custom fields so that they can be rearranged in different orders.
2. Create a request, filling in all fields with values.
3. Sort the fields in the request form differently and monitor the fields order of the fields in the created form.

Expected Results

Besides the Summary field, the order of fields in the created request should match the form order. Here's a screenshot of the created request and the form configuration in JSM 5.12.25.

Actual Results

Depending on the fields, sometimes the Assets fields are grouped together in their own sequence (matching the form order, but without the non-Assets fields mixed in). This can be reproduced when Assets fields are not place at the first/last place of the form.
The screenshot below illustrates this, showing Asset fields grouped and placed first. Non-Asset fields like Priority, Labels, and Components remain in the form order.
The Assets field in the first place and the last place will retain its sequence in the created request.

Workaround

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

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: