Issue Summary

When retrieving issues via the Jira Get Issue API, the list of sprints associated with an issue is returned in a non-chronological, seemingly random order. This causes confusion for users and integrators expecting sprints to be ordered by when it got associated with the issue.

Steps to Reproduce

1. Create several sprints on a Jira board (e.g., Sprint 1, Sprint 2, Sprint 3), possibly out of sequence.
2. Associate an issue with these Sprints. (e.g., carry it over from Sprint 1 to Sprint 2, then to Sprint 3).
3. Use the Jira REST API (e.g., /rest/api/3/issue/ {issueIdOrKey}

   ) to fetch the issue details, including the Sprint custom field.

4. Observe the order of sprints in the API response.

Expected Results

The sprints array in the API response should be ordered in a predictable manner, such as the order they got added to the issue. If this is followed, the last Sprint should be at least an active/future Sprint.

Actual Results

The sprints array is ordered randomly, which may not match the chronological or expected sequence.

Workaround

Users currently sort the Sprints array using metadata to find the active/future sprint, this shows that this was the last added Sprint, but this won't work if they want to know the first Sprint associated with the issue or in scenario where all Sprints are closed and want to know which was added n(first), n+1, n+2,......