-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Component/s: Teams - On-call - Schedules
-
None
-
4
-
Severity 3 - Minor
Issue Summary
The order responders are returned in this endpoint no longer respects the order in which they are on-call. Specifically, the list returned in the exactNextOnCallRecipients may not be in the order the responders will be on-call.
https://docs.opsgenie.com/docs/who-is-on-call-api#get-next-on-calls
Steps to Reproduce
- Create a schedule with two on-call rotations.
- Perform a get next on-calls API request: https://docs.opsgenie.com/docs/who-is-on-call-api#get-next-on-calls
Expected Results
The next on-call users in both rotations are returned in the order of their on-call shifts.
Actual Results
The next on-call users in both rotations are returned but the order may not be in the order they are on-call.
Workaround
Using a single rotation in a schedule, instead of multiple, will mean the next on-calls endpoint will always respect the order of that rotation.