Installation and Setup Guide

Out of Office Assistant runs on Atlassian Forge inside Jira Cloud. This guide covers installing it from the Atlassian Marketplace, approving what it asks for, confirming it is running, and the setup steps only an administrator can do.

Before you start

• You need Jira administrator rights. Installing an app is an administrator action.

• The app is Jira Cloud only. Forge apps do not run on Jira Server or Data Center.

• The app is licensed for the whole site, following Atlassian's standard licensing model. See Licensing below.

If you are moving from the Connect version, you are upgrading rather than installing: it is the same Marketplace listing, and your existing configuration is carried over automatically. Migrating from Connect to Forge lists what comes across and what you have to recreate.

Install the app

1. In the Jira sidebar, open Apps, then select Explore more apps at the bottom of the list. The Atlassian Marketplace opens inside Jira.

2. Search for out of office.

3. Open the listing named Out of Office Automation for Jira (Outlook, Google, Tempo), published by resolution Reichert Network Solutions GmbH.

4. Select Try it free and follow Atlassian's prompts to choose the site you are installing on.

5. Review what the app requests: the Jira data it needs and the external address it connects to, then approve it. The app cannot run until you do.

6. Wait for Atlassian to confirm the installation.

The listing is also reachable directly on the Atlassian Marketplace: https://marketplace.atlassian.com/apps/1218305/out-of-office-for-jira-team-calendar-absence-automation?hosting=cloud

What the app asks for at installation

The app connects to Microsoft Outlook, Google Calendar, Slack and Tempo, but never reaches them directly. Those connections are routed through Customer Managed Egress, which sends them all through a single external address. Two things follow:

• Only a single egress URL has to be allowed when the app is installed.

• Connecting an integration later does not raise a new consent prompt. Once the initial request is approved, users connect their own accounts without an administrator approving anything further.

What the app stores and where is described on Privacy and Security.

Confirm the installation

In the Jira sidebar, open Apps and select Out of Office Assistant under Your apps. The app opens on the Team Availability tab; its six tabs are the entire navigation.

The app's Team Availability tab.

You can also check from Atlassian Administration, under Site settings > Connected apps. The Installed apps tab lists every app on the site with its edition and who installed it.

If the app is not listed once installation finishes, check that you are signed in to the site you installed it on. If it still does not appear, raise a ticket with our support team: https://resolution.de/go/support

Licensing

Out of Office Assistant follows Atlassian's standard licensing model for Cloud apps: one subscription covers every user on your Jira site, at the same user tier as Jira itself. There is nothing to assign or enable per person. The app does check that the subscription is valid before it acts, and without one:

• The app's controls are locked or hidden.

• Scheduled jobs stop running.

• Work items are no longer reassigned automatically, even where a rule is active.

• The Out of Office section on a work item shows an unlicensed message instead of the assignee's availability.

The subscription is handled by Atlassian, not inside the app, so a lapsed one is fixed in Atlassian Administration rather than in App Settings. Pricing and trial terms are on the Marketplace listing.

Set up the app

Four things need an administrator once, and a fifth if you run Jira Service Management.

1. Decide who administers Out of Office. Open App Settings > Permissions and name your Space Admins and Out of Office Admins. This is the step most often missed after an upgrade: granting someone Jira space administration rights does not let them manage other people's Out of Office rules. See Permissions and Access Requirements.

2. Set the site-wide behaviour. Open App Settings > General Settings, which has three groups: Mentions in Comments decides whether an out of office tag is added beside @-mentions of absent people, Service Management picks the service management spaces that show agent availability in the customer portal, and Inactivity Tracking sets after how many idle days a user is marked inactive. See Out of Office Admin Quick Reference Guide.

3. Set up the integrations you need. Tempo and Microsoft 365 are configured once for the whole site under App Settings > Global Integrations. Outlook, Google Calendar, Slack and personal REST API tokens are connected by each person from their own My Integrations tab. See Integrations.

4. Decide who may create REST API tokens. Open App Settings > Rest API Permissions and set Who can create REST API Tokens to all users, the default, or to named users only. An ADMIN-scope token reaches every user's rules, so this is a security decision, not a convenience one. See REST API Endpoints Documentation.

5. If you run Jira Service Management, choose the portal spaces. Under App Settings > General Settings > Service Management, the spaces you select show an agent availability section to customers in the portal. Portals in every other space show nothing. See Agent Availability Display in JSM Customer Portal.

Related pages

• Out of Office Quick Start Guide - create your first rule.

• Interface Tour and Navigation Guide - what each of the six tabs does.

• Permissions and Access Requirements - who can do what, and how each role is granted.

• Migrating from Connect to Forge - what changes if you used the Connect version.