Issue Summary

There is an inconsistency across Jira clients (Jira Web, Android Mobile App, and iOS Mobile App) regarding how the Sprint field dropdown filters and orders available sprints when viewing or editing an issue.

• Board-level scoping: The iOS Jira Mobile App filters the Sprint dropdown to show only sprints from the board the issue belongs to (grouped by board name), whereas Jira Web and the Android Mobile App display sprints across all accessible boards site-wide.

• Sprint ordering: The iOS Jira Mobile App displays sprints in chronological order, whereas Jira Web and the Android Mobile App list sprints out of chronological order (relying on backend sequence/ID values).

Steps to Reproduce

1. Create multiple active and future sprints with distinct start/end dates across multiple Scrum boards on the site.
2. Open an existing Jira issue that belongs to a specific Scrum board.
3. Edit the Sprint field and observe the sprint list across different clients:
   • Edit via the iOS Jira Mobile App
   • Edit via the Android Jira Mobile App
   • Edit via the Jira Cloud Web interface

Expected Results

The Sprint dropdown behaves consistently across all platforms (Web, Android, iOS) by scoping available sprints to the issue's relevant board and listing them in chronological sequence.

Actual Results

• iOS Mobile App: Contextually filters to the issue's board and displays sprints in chronological order.
• Android Mobile App & Jira Web: Displays all active and future sprints across all boards site-wide without board scoping, and displays them in non-chronological order.

Workaround

• Assign issues to sprints directly from the Backlog view of the relevant Scrum board rather than using the Sprint field dropdown in the Issue View.
• Adopt a standardized sprint naming convention (e.g., [Board/Project] YYYY-MM Sprint X) and search explicitly for the sprint name in the dropdown picker.