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

Out of Office on Atlassian Forge

Released 31 August 2026. Out of Office Assistant now runs on Atlassian Forge rather than Atlassian Connect. This is the largest change the app has had. The platform underneath it is different, every tab was renamed, and three things an administrator set up before have to be set again afterwards.

How your instance is upgraded

An administrator starts the upgrade and the app does the rest. In Atlassian Administration open Connected apps, find Out of Office Assistant in the list and select Update. Inside Jira, Apps > Manage your apps leads to the same screen.

Nothing else is asked of you. There is no import step and no export to prepare beforehand. Rules continue to run through the upgrade. When the Forge app is installed or upgraded it reads the configuration held by the Connect app, writes it into its own storage, and marks the installation as migrated, so a later upgrade does not transfer the same data again. Your rules, your Tempo integration configuration and your general settings come across, and an existing Slack connection keeps working without being reconnected.

If the upgrade does not complete, or something is missing afterwards, raise a ticket at resolution.de/go/support and name your site address. You can also reach us from the app itself: the Support tab has a Contact us button under Need Help?. Do not reinstall the app to try to fix it.

What an administrator sets again afterwards

  1. JQL search aliases. Forge does not allow a dot inside a search alias, so outofoffice.today is now outofoffice-today, and the other five aliases change the same way. This is the one change that can go unnoticed: a saved filter, board card colour rule or dashboard gadget written with a dotted name raises no error, it simply stops returning anyone who is away.

  2. The spaces each space admin covers. Space admin delegation must now name specific spaces. The Connect version's all projects option is gone, and a migrated instance prompts you in App Settings > Permissions to reselect them.

  3. REST API tokens, if you build new integrations. Tokens are not copied across, because the Forge app answers on a different REST base URL. Integrations already running against the Connect app keep working: a request it forwards with a token it issued is still accepted.

Migrating from Connect to Forge gives each of these step by step, with the full alias table.

What is new in this release

  • Recurring rules. A rule can repeat: tick Make the rule recurring, set Repeat every N week(s) and choose the weekdays it applies to.

  • Absence data in Jira search. The app publishes six absence fields, read through a user field as in assignee.outofoffice-today = 1, which drive saved filters, service desk queues, dashboard gadgets and board card colours.

  • Rebuilt app settings. Site-wide configuration is one tab, App Settings, divided into General Settings, Permissions, Global Integrations and Rest API Permissions. Changes there save as you make them; there is no Save button.

  • An integration filter that matches your site. The filter on Team Availability no longer offers global integrations an administrator has not configured. Personal integrations are always listed.

What was removed

The Zapier integration is not part of the Forge app. The page describing it stays published for customers still on the Connect version, under Archive (Connect version).

Where the screens moved

All six tabs were renamed, so an instruction written for the Connect version will not match what you see. User view is now Team Availability, Rules is My Rules, Integrations is My Integrations, Settings is App Settings and Customer Support is Support. The separate administration screen is gone. The Templates Library is no longer a tab of its own; templates you own sit under My Templates, and the shared library is a picker inside an integration, reached from Add template from library.