Out of Office Assistant for Jira CloudOut of Office Assistant for Jira Cloud
Try For Free

FAQ

These pages answer questions that come up once Out of Office Assistant is installed and people are creating rules. Each page collects short answers on a single topic.

If you are looking for instructions rather than answers, start with Getting Started, which runs from installation through to a first working rule, and Features, which has a page for each part of the app.

Setting up and administering the app

  • Setup and Installation - what an administrator needs before installing the app, where its screens appear afterwards, and what one installation covers: licences, spaces and rollout.

  • User Permissions - who may create or change a rule for somebody else, who can see another person's absence, and which of those an administrator decides centrally.

  • Security and Privacy - where the app runs and what it reaches, what a rule records about an absence, who can see it, and how to make a data access or deletion request.

Rules and coverage

  • Rule Configuration - ending a rule early, repeating one, holding several at once, and narrowing a rule to part of a day or to particular work items.

  • Automations and Workflow - running Jira's own automation next to the app, including what to do when automation keeps assigning work to somebody who is away.

  • Notifications - who hears about an absence and when, from the point a rule is scheduled to the work items it hands over.

Connecting other tools

  • Calendar Integrations - connecting Office 365 (Outlook) or Google Calendar, which events turn into a rule, and what becomes of that rule when the event moves or is cancelled.

  • Tempo Integration - how a Tempo Planner plan becomes Out of Office rules, why one plan can produce several, and what an individual can still change on an integration an administrator manages.

  • API & Connectivity - what the REST API can read and change, and how its tokens are issued and who is allowed to create them.

Service management and troubleshooting

  • Jira Service Management & ITSM - seeing which agents are away, what happens to a request and its approvals while the agent is out, and what the customer portal shows.

  • Troubleshooting - a handover that did not happen, work that keeps coming back to the person who is out, and an integration that stopped producing rules.

  • Integrations - the five integration cards, one page each: Office 365 (Outlook), Google Calendar, Slack, Tempo Planner and the REST API.

  • JSM Features - the four things specific to a service desk: approval delegation, service desk customer notifications, the portal availability panel, and rules for portal customers.

  • Quick Reference Guides Jira Out of Office - one-page summaries for six roles: end users, Out of Office admins, space admins, Jira admins, service desk agents and portal customers.

  • Migrating from Connect to Forge - what carries over when a site moves to the Forge version, and what must be recreated.