Issue Summary

REST API parameter startAt is not bringing consistently when fetching Custom Fields.

Steps to Reproduce

1. Execute the following REST using any value at the startAt or maxResults

   GET /rest/api/2/customFields?startAt=2&maxResults=15

• Important to say that the two parameters can have any value, the result will never get the right ones.
  Get the following result:
  

  Expected Results

1. Execute the following REST using any value at the startAt or maxResults

   GET /rest/api/2/customFields?startAt=2&maxResults=15

2. Get the right number on the startAt and MaxResults at the page.
   The expected result would be to get the right values on startAt or maxResults

Actual Results

1. Execute the following REST using any value at the startAt or maxResults

   GET /rest/api/2/customFields?startAt=2&maxResults=15

2. Getting the results below.
   
   The amount of custom fields on the instance does not seem to affect the behavior it was tested on an instance with 16 and another instance with 40 custom fields, the result is the same.

Workaround

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