GraphQL API not following Start and Limit index values correctly when there is a JQL Order By clause

Description

GraphQL API not following Start and Limit index values correctly when there is a JQL Order By clause.

If a JQL is used to search for a list of Issues, the Start Index "Position 0 Issue" is showing in the response as the first issue in the list, starting the list from top to bottom.

However, if an Order By clause is added to the JQL, the Start Index "Position 0 Issue" is showing in the response as the last issue in the list, starting the list from bottom to top. 

Pre-conditions

• Have a list of Issues to search

How to reproduce

• Create a GraphQL "getTests" query using a JQL to search for a list of issues:

• • Include Start: 0 and Limit: N
• Run the query request and notice the First and Second Issue from top to bottom
  • If we change the Start to 1 and run the query again, we will notice the Second Issue is showing as the first position in the list from top to bottom.
• Now, add an Order By to the JQL and use Start: 0
• Run the query request and notice the Last and Second to Last issues in the list
  • If we change the Start to 1 and run the query again, we will notice the Second to Last Issue is now showing as the Last position in the list.

• Video Example: Insomnia_JxlWvvn2Tz.mp4

Actual result/Attachments

If the JQL does not contain an order by:

The position 0 Issue will always show as the first issue in the list, at the top of the list (from top to bottom) .

If the JQL contains an Oder By:

The position 0 Issue will always show as the last issue in the list, at the bottom of the list (from bottom to top) .

Expected result

The position 0 Issue should always be shown as the First Issue in the list, from top to bottom.