Bitbucket Push Logs don't display the commits in chronological order

Issue Summary

On Bitbucket Push Logs page, the customer has reported that on switching branches, the latest commits are not visible.

This is reproducible on Data Center: yes

Steps to Reproduce

• Create atleast 2 new branches other than the master branch and perform >50 pushes in each.
• Goto the push log page, the master branch is shown.
• Switch to another branch having > 50 pushes. Note the from ref in the first row matches the from hash in the response of the API call for the first value on the first page. also note the timestamp.
• Scroll down half way to load only one more API call and not all
• Now switch the branch to the other branch having > 50 pushes. This time start=0 and start=50 params API are called at the same time and the paging is displayed incorrectly. ( mostly timing issue to load the response as the response payload comes at the same time ).
• Note the from hash for the start=0 API. This appears midway on the page and the last API page response is shown at the beginning
• If we switch back to the previous branch, similar issue occurs here as well.

Expected Results

The push logs must be displayed in proper order of the API paged responses starting with the latest logs and then the previous ones.

Actual Results

The push logs are not displayed in the correct chronological order. Refer attached images.
2 images have the same test_branch with different commits on the first row.

Workaround

To get the latest push logs using Bitbucket Get ref change activity API