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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Morning & Afternoon shift in oncall

I'm trying to create a morning and an afternoon shift. They should not be handled by the same person ever. The night is taken by an actual oncall schedule which is separate and works fine and doesn't need changing in this context.

But the result for me is, that the shifts don't actually align at 50% each, but get this weird fragmentation pattern, even when making two distinct slots and a rotation of exactly the hours length of the slots (which already is annoying since for us it would actually be 4.5 hours each, but even at 5 hour each it still doesn't work).

The only way I have found to get rid of those, is to have two entire schedules again, but then the system doesn't give you any option I can find to ensure both schedules aren't given to the same person, if the same people are in the pool for both schedules, which for us they are.

Does anybody have an idea what else we could do to have two daytime shifts, each assigned to one person in its entirety and not the same person for both on one day?

Attached the failed schedule fragmentation and my attempted settings.



1 answer

0 votes
John M
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 30, 2023

Hi @Patrick Robinson ,

There is a bit of a limitation with Opsgenie here, in that it builds the rotation out, and then adds time restrictions - so the restrictions don't come into play until after the shift length has been calculated.

In other words, the random shift lengths are caused by the gaps where there is no on-call user, but shift times are still calculated, which appears to throw off the visible time-restricted schedule. I have submitted the following bug for our development team to review:

The workaround would be to add the users on separate rotations. 

As I said I tried separate rotations. With the same users in both, it virtually always scheduled both shift to the same person, which may never happen. That's the concept of having shifts.

There is an answer in the ticket you mentioned. Summarizing for posterity:

If you set the rotation length to 6 hours and start at 7:00, you can setup the shifts as you desire, I assume as long as switchover is 13:00 or adjust start time if it isn't. The shifts don't need to be 6 hours for that.


John M
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 01, 2023 • edited

@Patrick Robinson  Changing the start time is a good option, but it will only work if the shift length is divisible by 24, which is why the developer used a 6-hour shift in his solution. With a 5-hour shift, the shift lengths will not stay consistent since 5 does not divide evenly into 24. 

Regarding the solution of using multiple shifts; you would need to add only one person to each shift. The only downside would be you would lose the 'escalate to next' option, which wouldn't matter if you're not using it. 


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events