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.
Only visible to you #(me)
my_organization_schedule Participants: engineer-1, engineer-2
However, a peer of mine has observed the following
Only visible to you #(peer)
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:
my_organization_schedule Participants: Secondary: engineer-2, Primary: engineer-1
Question: Has anyone else observed this behavior, or found a solution?
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
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...
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