Skip to content

Rule Configuration Guide

Overview

This guide provides detailed instructions for creating and configuring absence rules using Out of Office Assistant. Rules automatically manage issue assignment and communication when team members are away from work.

Understanding Rule Configuration

Rule Lifecycle

Out of Office rules follow a predictable lifecycle:

  1. Creation: Rule defined with dates, scope, and handling instructions

  2. Scheduled: Rule waiting for start date to activate

  3. Active: Rule processing issues and executing actions

  4. Expired: Rule past end date, no longer processing issues

  5. Disabled: Rule manually deactivated but preserved

out_of_office_rules_dashboard - 01.webp

Rule Components

Every rule consists of:

  • Timing: Start date (required) and optional end date

  • Scope: Which issues the rule affects (projects or JQL filter)

  • Handling: How issues are processed (coverer, approval, or message)

  • Options: Additional behaviors like mention tags and custom messages

Accessing Rule Configuration

out_of_office_rules_dashboard.webp

Open Out of Office Assistant

  1. Navigate to Apps → Out-Of-Office Assistant 

  2. Verify you see the main interface with rules table

Start Rule Creation

  1. Click the blue “Add rule for myself” button in the top right 

  2. Rule creation form opens with complete configuration options

Rule Configuration Form

schedule_out_of_office_rule.webp
Create out of office rule

Essential Configuration Fields

Start Date (Required)

Purpose: Defines when your absence rule begins
Requirements: Must be set - rule cannot be created without start date

Configuration Steps:

  1. Click the Start Date field (marked with red asterisk *)

  2. Select date using the calendar picker

  3. Time defaults to 12:00 AM in your timezone

  4. Timezone information displays below field (e.g., “Europe/Berlin (+02:00)”)

Best Practices:

  • For planned absences: Set start date to the first day you’ll be away

  • For immediate activation: Select today’s date or past date

  • For future planning: Use specific start dates for vacation scheduling

End Date (Optional)

Purpose: Defines when your absence rule automatically deactivates
Default: If left empty, rule continues indefinitely until manually disabled
Timezone: Uses same timezone as start date

Configuration Options:

  • Specific End Date: Rule automatically deactivates at end date

  • Indefinite Duration: Leave empty for manual deactivation control

  • Return Planning: Set end date for day you return to work

Usage Recommendations:

  • Vacation: Always set specific end date

  • Sick leave: Leave empty for uncertain return date

  • Extended projects: Set end date for project completion

Scope Configuration

Project Scope (Default)

All Projects (Recommended for Most Users):

  • Rule applies to all Jira projects you have access to

  • Issues assigned to you in any project will be affected

  • Simplest configuration for comprehensive coverage

Specific Projects:

  • Click the “All Projects” dropdown

  • Select specific projects where rule should apply

  • Useful for role-based absence management

JQL Issue Filter (Advanced)

When to Use:

  • Complex issue filtering requirements

  • Specific issue types or statuses

  • Custom business logic for issue selection

Configuration:

  1. Select “JQL Issue Filter” radio button

  2. Select existing Jira Filter or Create a Custom Filter 

  3. Test JQL in our Out of Office Preview or in Jira Issue Search

JQL Examples:

  1. # All issues in specific project
  2. project = "MY PROJECT" AND assignee = "user.account.id"
  3. # Only bugs and stories
  4. project = "MY PROJECT" AND issuetype IN (Bug, Story) AND assignee = "your user ID"
  5. # High priority issues only
  6. priority = High AND assignee = "user.account.id"
  7. # Issues with specific labels
  8. labels = urgent AND assignee = "user.account.id"

JQL Best Practices:

  • Always include assignee = "user.account.id" for personal rules

  • Test JQL queries before using in rules

  • Keep filters simple for reliable operation

  • Document complex JQL for future reference

Issue Handling Configuration

Coverer Assignment (Most Common)

Out-of-Office assistant will assign new issues during your absence to your coverer.

Approval Delegation (JSM Projects)

Out-of-Office assistant will assign approval requests in JSM projects to your coverer

Custom Message (Auto Reply)

Out of office assistant adds a comment to issues which are assigned to you during your absence with your individual message.

Status-Only Rules

Status-Only Rules display your Out-of-Office status without automatically reassigning issues. These rules inform colleagues about your availability in the Issue Context.

Requirement: Must configure at least one handling method.

Option 1: Coverer Assignment (Most Common)

Purpose: Reassign issues to colleagues who will handle them during absence

Configuration:

  1. Click “Coverer(s)” dropdown

  2. Type colleague’s name - dropdown filters as you type

  3. Select user from dropdown when name appears

  4. Add multiple coverers for round-robin assignment

Coverer Selection Criteria:

  • Permissions: Coverer must have assignment permissions in relevant projects

  • Availability: Verify coverer is available during your absence period

  • Skills: Choose coverer with appropriate expertise for your issue types

  • Workload: Consider coverer’s current workload and capacity

Multiple Coverers:

  • Round-robin assignment: Issues distributed among multiple coverers

  • Load balancing: Helps prevent overwhelming single coverer

  • Backup coverage: Provides redundancy if one coverer becomes unavailable

Option 2: Approval Delegation (JSM Projects)

Purpose: Delegate approval responsibilities in Jira Service Management projects

Restrictions

  • JQL-based rules are not supported for approvers

  • Groups of approvers are not supported

  • Only a single approver coverer is supported.

  • Changes to the workflows governing the approval processes may result in the app not being able to delegate approvals for existing issues that went into the approval process before the last change to the workflow.

When to Use:

  • You have approval responsibilities in JSM projects

  • Customer requests require approval during your absence

  • Service level agreements must be maintained

Configuration:

  1. Coverer for Approvals:

  • Select colleague who will handle approval decisions

  • Must have appropriate permissions in JSM projects

JSM-Specific Considerations:

  • Customer Impact: Approvals affect customer experience directly

  • SLA Compliance: Ensure approval delegation maintains service levels

Option 3: Custom Message Only

Purpose: Notify stakeholders about absence without reassigning issues

When to Use:

  • You prefer to handle issues yourself upon return

  • Temporary absence where reassignment is not needed

  • Communication-only requirement for transparency

Configuration:

  1. Type message in “Out of Office Message in Issue Comments” text area

  2. Include essential information:

  • Return date (if known)

  • Emergency contact information

  • Alternative resources for urgent matters

Message Best Practices:

  1. I'm currently out of office until [return date].
  2. For urgent matters, please contact:
  3. - [Colleague Name]: [email] for [specific type of issues]
  4. - [Manager Name]: [email] for approval decisions
  5. I'll respond to non-urgent matters upon my return.

Option 4: Status-only Rules

Option 1: Coverer Assignment (Most Common)

Purpose: Visibility without delegation: Shows you're away without transferring work. Displays your status in the Issue Context

Configuration:

  1. Choose Status-Only Rule type

When to Use:

  • Visibility without delegation: Shows you're away without transferring work

  • Absence communication: Displays your status and custom message

  • Flexible availability: Ideal for non-traditional schedules

  • Integration support: Works with all Out-of-Office integrations

Advanced Configuration Options

Out of Office Message

Purpose: Custom message posted to issue comments when rule processes issues
Compatibility: Works with all handling methods (coverer, approval, message-only)

Message Configuration:

  • Custom Content: Add specific instructions, contact information, timelines

  • Professional Tone: Keep messages clear and helpful for issue stakeholders

Message Examples:

With Coverer:

  1. I'm currently out of office until [date]. [Coverer Name] will be handling my issues during this time.
  2. For urgent matters, please contact [Coverer Name] directly at [contact].

Message Only:

  1. I'm currently out of office until [date]. This issue will be addressed upon my return.
  2. For urgent assistance, please contact [backup contact] or escalate through your project manager.

Mention Tag Options

Purpose: Add visual indicators to issue comments for stakeholder awareness

Tag Options:

  • Don’t add an out of office tag (Default): 

    • No visual indication added to issues 

    • Clean issue appearance 

    • Recommended for internal teams with good communication

  • Add an out of office tag, when out of office

    • Tag appears when rule is active 

    • Immediate visual indicator of absence status 

    • Useful for customer-facing projects

  • Add it 4 days ahead of the absence

    • Early warning for stakeholders 

    • Allows planning and coordination 

    • Recommended for planned vacations and critical role absences

Tag Benefits:

  • Visual Awareness: Immediate indication of user availability in comments

  • Planning Support: Advance notice helps team coordination

Rule Configuration Workflows

Quick Setup for Vacation

Timeline: 2–3 minutes for standard vacation rule

  1. Start Date: First day of vacation

  2. End Date: Day after return (for safety buffer)

  3. Scope: All Projects

  4. Coverer: Select trusted colleague

  5. Message: Include return date and emergency contact

  6. Mention Tag: “Add it 4 days ahead” for advance notice

Emergency Sick Leave Setup

Timeline: 1 minute for immediate activation

  1. Start Date: Today’s date (or yesterday if retroactive)

  2. End Date: Leave empty (uncertain return)

  3. Scope: All Projects

  4. Coverer: Select available colleague or manager

  5. Message: Brief explanation with contact for urgent matters

  6. Mention Tag: “When out of office” for immediate indication

Project-Specific Absence

Timeline: 3–5 minutes for targeted configuration

  1. Start Date: Project absence start

  2. End Date: Project timeline completion

  3. Scope: Select specific projects OR use JQL filter

  4. Coverer: Project team member with relevant expertise

  5. Message: Project-specific instructions and contacts

  6. Mention Tag: Based on project visibility requirements

Service Desk Agent Configuration

Timeline: 5 minutes for complete JSM setup

  1. Start Date: Service absence start

  2. End Date: Return to service date

  3. Scope: JSM projects only (use JQL: project IN (serviceDesk1, serviceDesk2))

  4. Approval Delegation: Select backup agent with customer permissions

  5. Message: Customer-friendly language with service alternatives

  6. Mention Tag: “Add it 4 days ahead” for customer planning

Form Submission

Successful Submission:

  1. Click “Submit” button when all requirements met

  2. Return to main interface automatically

  3. New rule appears in rules table

  4. Status shows “Scheduled” (future start) or “Active” (current/past start)

Cancellation:

  • Click “Cancel” to return without saving

  • No data preserved - must restart configuration if needed

  • Confirmation dialog may appear for complex configurations

Rule Management After Creation

Rule Status Indicators

Scheduled: Rule created but start date not reached
Active: Rule currently processing issues
Expired: End date passed, rule no longer active
Disabled: Manually deactivated but preserved

Rule Modification

Edit Existing Rules:

  1. Click menu button (three dots) in Actions column

  2. Select “Edit Rule” from dropdown

  3. Modify configuration as needed

  4. Submit changes to update rule

Quick Enable/Disable:

  • Toggle switch in Actions column for immediate state change

  • No confirmation required for toggle operations

  • Rule configuration preserved when disabled

Best Practices Summary

Planning and Preparation

  1. Plan Ahead: Configure rules at least 24 hours before absence

  2. Communicate: Inform team members about coverer assignments

  3. Test: Create test rules for complex configurations

Configuration Choices

  1. Start Simple: Use “All Projects” scope for first rules

  2. Choose Appropriate Coverers: Select based on availability and expertise

  3. Set Clear Messages: Include return dates and emergency contacts

  4. Use Mention Tags: Provide advance notice for planned absences

Maintenance and Updates

  1. Monitor Active Rules: Check status and effectiveness regularly

  2. Update as Needed: Modify rules if circumstances change

  3. Clean Up: Disable or delete expired rules

  4. Learn and Improve: Refine approach based on experience


Rule Configuration Status: ✅ COMPLETE
Next Stephttps://resolution.atlassian.net/wiki/spaces/OoO/pages/4848353576