-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Mobile Apps
-
None
-
1
-
Severity 3 - Minor
-
1
Issue Summary
JSM Ops Mobile App fails to create overrides on schedules that have no rotations. The mobile app renders a phantom/blank entry in the "Select Rotation" picker and submits an invalid rotation ID, resulting in the error: "Override cannot contain non existing rotation id." This issue does not occur on the Web UI, via the REST API, or when using the "Take on-call for 1 hour" option on mobile.
Steps to Reproduce
- Create a schedule without adding any rotations.
- Add an override via the WebUI or API for this schedule
- Open the schedule in the Jira mobile app
- Attempt to create a new override from the mobile app
- Observe the "Select Rotation" picker shows a blank/empty entry.
- Submit the override.
Expected Results
Override creation should work consistently across all clients (Web UI, API, and Mobile App), or the mobile app should display a clear and informative message if rotations are required
Actual Results
The mobile app throws the following error:
Override cannot contain non existing rotation id
Workaround
- Create overrides via the Web UI or REST API, both of which handle the no-rotation scenario correctly.
- Add at least one simple rotation to the schedule. Even a single-participant rotation resolves the issue and aligns with the intended schedule design (Schedule → Rotation → Participants → Overrides)