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

Assign issues during working/non-working hours to agents and Opsgenie on-call schedule


You are looking to assign issues to Service Desk Agents using a round robin schedule during working hours, however, during off-hours you would like to route the new tickets to the On-call Responder.

This is most certainly possible, please see the screenshots below of this configuration:

Screenshot 2023-01-26 at 9.08.02 AM.png

JQL to use for this use case

Please note that the (9h) startOfDay value can be changed to any start time for a working day, and so can the end of the day (where the (17h) value is):

Non Working Hours:

created < startOfDay(9h) AND created > startOfDay(17h) 

Working Hours:

created >= startOfDay(9h) AND created <= startOfDay(17h) 


If block for Working Hours

Screenshot 2023-01-26 at 9.08.19 AM.png

Assign Issue to a User Group via Round Robin assignment (can be any group you choose)

Screenshot 2023-01-26 at 9.08.27 AM.png

Else block for Non-Working Hours

Screenshot 2023-01-26 at 9.08.39 AM.png

Assign Issue to On-call Schedule in Opsgenie

Screenshot 2023-01-26 at 9.08.49 AM.png


Please note that the Automation Rule Actor should ideally be an Org Admin for your Atlassian Organization. This will ensure that the necessary admin permissions are applied to the Automation Rule, as you cannot use the Automation for Jira Actor currently, due to a Short Term Backlog Bug:


Example setup of Org Admin for Automation Rule Actor

Screenshot 2023-01-26 at 9.33.01 AM.png


I hope this helps!



Christian B.



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events