Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,644
Community Members
 
Community Events
185
Community Groups

Can rotations in OpsGenie divert to other rotations?

Let's say I have a Rotation A, filled with the following people:

Matt, Kim, James, Mary, Rowena

Now I want to start up a rotation B but I only have three engineers to stock it for now, Ashley, Bob, and Charlie. That's not enough for my liking, so in the fourth week of each rotation, I'd like to essentially delegate to Rotation A for any alerts on Rotation B.

This effectively means that Rotation B might end up looking something like:

Ash -> Bob -> Charlie -> Mary -> Ash -> Bob -> Charlie -> James -> etc

Is this even possible in OpsGenie? I note that you can have "Teams" as participants in rotations, but I suspect the end result of doing that would be _everyone_ in the team would be notified during that week if an alert was raised - and that's not what I want.

1 answer

1 accepted

0 votes
Answer accepted
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 01, 2022

Hi @David Meacock ,

I think that's possible, and I'll provide some suggestions below of the use case you mentioned, but it might require some unique configuration.

Let's say for the sake of this example:

Ash = User 1 
Bob = User 2
Charlie = User 3
Matt = User 4
Kim = User 5
James = User 6
Mary = User 7
Rowena = User 8

 

 You could combine all of these users into one rotation, and add Users 1-3 multiples times in between User 4-8 with something like this:

rot1.jpg

 

Another option is breaking this into two rotations where:

Rotation A: Ash, Bob, Charlie

Rotation B: Matt, Kim, James, Mary, Rowena

and represent the "skipping" shifts with the option No one to account for something like: 

Ash -> Bob -> Charlie -> Mary -> Ash -> Bob -> Charlie -> James -> etc

 

Example:

rot2.jpgrot3.jpgrot4.jpg

 

Regardless, I think it's possible - but not the most ideal situation due to the skipping for Rot A >> B >> A >> etc. Hope that helps.

Thanks Nick, unfortunately not quite what I'm after due to the overhead of having to manually enter everyone as individuals. If Rotation B was to change, I'd prefer this rotation to change with it rather than having to manually edit both. 

I'll take the answer to my original question as being "no" for now, while acknowledging there's some workarounds that can be done - thanks!

Like Nick H likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events