In this article, we walk you through how to set up permanent delegation in Jira to automate shift rotations, on-call handovers, and approval reassignments, eliminating the need for manual cleanup, Slack announcements, or calendar reminders. By configuring structured coverage rules with Out of Office Assistant for Jira and JSM, your team can keep queues moving 24/7 without relying on human memory.
We hosted a live webinar demonstrating exactly how to configure these delegation rules inside Jira so your system understands who is responsible at all times, automatically.
Watch the full walkthrough in our webinar recording below:
The Real Problem: Jira Doesn’t Understand Your Shift Schedules
Most teams today manage their rotations and shift schedules outside of Jira. They rely on Confluence pages with rotation lists, Slack or Teams messages announcing who is on call this week, or Outlook and Google Calendar reminders that pop up on Monday mornings. The issue is that while these tools communicate shift changes to people, Jira itself has absolutely no awareness that anything has changed.
The result is predictable and painful. New tickets still get assigned to the wrong person. Approvals continue routing to someone who is offline or no longer on shift. Round-robin automations don’t exclude unavailable users. And ultimately, admins end up spending significant time manually reassigning issues every week — a process that simply does not scale, especially in larger organizations with frequent shift changes.
Human Memory Is the Weakest Link
Even when teams try to be disciplined about updating assignments, humans forget. Someone forgets to update the assignment role. Someone forgets to change the automation configuration. Someone forgets to reassign approvals. It only takes one missed handover for tickets to pile up, SLAs to breach, and customers to wait longer than they should. The core issue is that the process depends on human memory, and that is inherently unreliable.
What Is Permanent Delegation?
Permanent delegation means defining structured coverage in advance so that your Jira environment automatically knows who covers whom, when coverage applies, which issues are affected, and whether the covering person replaces the assignee, watcher, or approver. Once these structures are set up, everything works automatically, no weekly reminders, no manual cleanup, no Slack announcements, and no Outlook reminders.
This approach transforms Out of Office Assistant from a simple leave management app into a structural reliability tool designed for operational continuity, shift coverage, rotation coverage, and on-call coverage.
Live Demo: Automating Shift Handovers in Jira
In our live demonstration, we walked through a practical scenario. We have a support engineer called Alex whose shift has ended, and Maria is taking over his shift for the week. Instead of manually reassigning all of Alex’s tickets, we configured a permanent delegation rule to handle this automatically.
Setting Up the Delegation Rule
Using the Out of Office Assistant user administrator view, we accessed Alex’s profile and created a rule with the following configuration:
- The rule runs from Monday to Monday, covering the full week that Alex is off shift
- A JQL filter scopes the rule to only reassign work items that are not in “Done” status, because there is no need to reassign completed tickets to Maria
- Maria is set as the coverer, meaning all qualifying issues assigned to Alex will automatically transfer to her
- Since this is a regular occurrence and both team members are aware of the rotation, no comment message is required, though one can be added if needed
When we created a new ticket and assigned it to Alex, the system immediately reassigned it to Maria without any manual intervention. This happens automatically the moment the ticket is created or when the delegation rule’s date range becomes active.
Bulk Assignment for Immediate Updates
An important feature we highlighted is the bulk assign capability. If you create a rule where the start date has already passed, for example, you set it up on Thursday but the shift started on Monday, you can click the bulk assign button to immediately reassign all qualifying issues. Without this, the rule would only apply to new issues going forward from the moment of creation.
Approval Delegation in Jira Service Management
We also demonstrated how permanent delegation works for approvals in JSM. Using the same Monday-to-Monday timeframe, we set up a rule specifically for a Jira Service Management project where instead of selecting a coverer for assignments, we selected Maria as the approval delegate. When a new ticket was created that required Alex’s approval, the system automatically set Maria as the approver, ensuring no approval requests sit blocked while Alex is off shift.
Recurring Templates with Calendar Integrations
Because shift rotations are often recurring, Out of Office Assistant supports templates that integrate with Outlook, Google Calendar, Slack, and Zapier. For calendar-based templates specifically, you can configure a template once with your project scope, coverer, and message, and then use it repeatedly through your Outlook or Google Calendar. This means Alex can set up his every-other-week rotation as a recurring template and never have to manually configure the rule again.
Enterprise-Scale Scenarios
24/7 Regional Support Coverage
For global teams, permanent delegation enables time-based delegation chains. For example, Berlin handles support from 8:00 to 16:00, New York takes over from 16:00 to midnight, and Sydney covers midnight to 8:00. Instead of manually transferring tickets between regional teams, the system ensures that if Berlin does not resolve a ticket during their shift, it automatically moves to the New York team, and then onward to Sydney. Coverage flows seamlessly across time zones.
Weekly On-Call DevOps Rotations
In DevOps environments where a different engineer handles escalations each week, permanent delegation removes the need to manually update rotation assignments. You define the recurring rules once, and the system ensures the correct person receives escalation tickets each week without anyone having to remember or announce the change.
Backup Approvers for Leadership Workflows
When executive approvals are required and a VP or director is unavailable, critical decisions can be delayed for days or even weeks. With permanent delegation, you can configure a backup approver who automatically receives approval requests when the primary approver is out. No escalation gets blocked, and time-critical decisions stay on track.
Governance and Accountability
For larger organizations with specific hierarchies, automation alone is not enough, teams also need governance and traceability. The delegation rules created in Out of Office Assistant are visible and auditable, meaning you can trace exactly who was responsible for what and when. This accountability is valuable not only for internal reviews but also for compliance and audit purposes. When delegation is set up from the beginning with clear rules, mistakes are significantly reduced.
The Cost of Manual Delegation
We can quantify the impact of manual handover work. If an admin spends just two hours per week fixing assignments, that adds up to approximately 8 hours per month and 96 hours per year, more than two full working weeks spent solely on maintaining coverage manually. Now multiply that across multiple teams, and the overhead becomes substantial.
Permanent delegation eliminates this wasted time and, more importantly, it protects your SLAs, reduces ticket aging, prevents approval deadlocks, and improves your overall customer experience. It is not just a matter of convenience, it is about operational resilience.
Getting Started with Out of Office Assistant
If your team runs on shifts and Jira does not understand those shifts, you are running on risk. Permanent delegation removes that risk entirely. Out of Office Assistant for Jira and JSM is available on the Atlassian Marketplace where you can download and evaluate it for your own environment. The app supports both standard Jira projects and Jira Service Management projects, with integrations for Outlook, Google Calendar, Slack, and Zapier.
If you would like a personalized walkthrough tailored to your specific use case, our support team is happy to schedule a demo and help you understand exactly how the app can solve your shift rotation and delegation challenges. Simply reach out to our team and we will guide you through a setup that fits your workflow.
