Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

'Who is On Call API' only returns 'nextOnCallParticipants' for current rotation, rather than all.


We are implementing a feature to set a 'backup' caller who will be available for call in our software, this is generated when someone starts through the previous member of the same rotation. In cases where the next person to be on call has been over-ridden, we want to select the person who has been over-ridden to be the backup caller. 

The 'Who is On Call' currently correctly shows 'exactNextOnCallParticipants' for multiple rotations, however where we could expect 'nextOnCallParticipants' to show next on call for both rotations before overrides, this isn't the case. We only get 1 entry. 

The image describes our current example case. As CH comes online, HS will want to be on backup.

Screenshot 2020-08-25 at 17.31.43.png

Querying the 'Who is On Call API' for the next person to be on call is expected to respond with:





however we get:





We are unsure why HS is being omitted here other than because they are on a separate rotation, however CH is shown what ways do we have to access who was overridden if not for this endpoint?


Kind regards

1 answer

0 votes
Robert Atlassian Team Aug 27, 2020

Hi @Lee Herring !


That is the intended behavior for the on-call API - it lines up with how Opsgenie escalates issues within a single on-call schedule as well: image.png

Generally, rotations are meant to separate things like regional teams. If you are looking to set up a backup then the best option is to break that out into its own "backup schedule" instead of a backup rotation. That would give you a little more control over when to notify users in each of those rotations.


That will also let you pull who is on call and who is backup using the on-call endpoint here (albeit with two requests):


Please let me know if you're still running into issues getting this up and running, but it sounds like that might resolve most of the problems you're running into!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Opsgenie

New GitLab integration in Incident Investigation view

We launched the first version of the Incident investigation view in April of 2020 for Bitbucket Pipelines. Shortly after that, we added the ability to investigate deployment-related incidents in Opsg...

325 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you