REST API "search" action returns subtasks in wrong order

Subtasks within issue can be ordered, but REST API action search (POST) returns wrong order comparing to issue/<idOrKey> (GET), where order is correct (both with fields=subtasks)

It's problematic, because we need to synchronize bunch of issues with our system and with search we could get all data at once, but since subtasks order is invalid in search response, we have to sync each issue individually.