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

/genie whoisoncall - why is the ordering non-deterministic (or missing rotation labels)

Recently ran into an unexpected source of confusion with the opsgenie slackbot.  Specifically, querying whoisoncall returns the participants in a non-deterministic order, and without the rotation label. 

Our setup is fairly simple.  We have a single organization, with a single oncall schedule, that includes two rotations (Primary, Secondary).  

I see the following via slack, where engineer-1 is primary, and engineer-2 is secondary. This is good. 

/genie whoisoncall
Only visible to you #(me)
Oncall Schedules:
my_organization_schedule Participants: engineer-1, engineer-2

However, a peer of mine has observed the following

/genie whoisoncall
Only visible to you #(peer)
Oncall Schedules:
my_organization_schedule Participants: engineer-2, engineer-1

This feels incorrect - either they should be ordered based on rotation ordering, OR, the name of the rotation should be included as follows:

Oncall Schedules:
my_organization_schedule Participants: Secondary: engineer-2, Primary: engineer-1


Question: Has anyone else observed this behavior, or found a solution? 


1 answer

0 votes

Hi Kevin,

Experiencing a similar issue with a schedule with 2 rotations and a phone integration, OpsGenie appears to be picking randomly between the 2 rotations in the schedule to call first.

We thought it may have been alphabetical, but ruled that out by editing one of the users names.

Wondering the same, if anyone else has a solution

Suggest an answer

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

Investigate deployment-related incidents with Bamboo and Opsgenie together

Back in April of last year one of the major product announcements from Opsgenie was the launch of the Incident investigation view which created a deep connection between Bitbucket and Opsgenie, empow...

1,464 views 1 5
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