Up/down arrows are not following the established order on a form from a filtered list - Known Error

Up/down arrows are not following the established order on a form from a filtered list Description In a filtered list (Incidents in this case), where the incidents have been filtered based on a condition like Assigned to or Assignment Group, and the list is sorted based on the Number field, when the Assignment group for an incident is changed and the incident is saved, pressing the down arrow in the Incident form to go to the next incident based on the sorting, skips one record and goes to the next record in line.

Steps to Reproduce

Pre Requisites: Create a filtered list of Incidents based on Assigned to field.

1. Open the first incident of a filtered list of incidents, sorted numerically.

2. Click the down arrow to see the next incident in numerical order to verify that the order is maintained.

3. Make a change to the assignment group of the current incident.

4. Save and observe the form reloads with the new assignment group in the field.

5. Hit the down arrow to advance to the next numerical incident. The incident number that shows is the second number in the list from the number that was changed, not the immediate next number in order. In other words, the down arrow action skips the next incident number and jumps to the one after that.

Workaround This is expected behaviour when updating data which does not match the query condition anymore, resulting in corrupting the original list output set.

At the time of saving the record, the only way to not to go to the second record and show the first again is to see if the changes done while saving are on the filter fields, in which case the sysparm_record_row count does not increase. This can not apply because the update is coming from a different place, not from the record itself.