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 note lists what shipped with the move. Everything released after it, up to version 3.17.0, is on Updates After the Forge Release (3.17.0). How to upgrade and what to check afterwards is on Migrating from Connect to Forge.

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.

  • App Settings tab. Site-wide configuration is one tab, App Settings, which only Jira admins see. It has four sections: General Settings, Permissions, Global Integrations and Rest API Permissions. Changes there save as you make them; there is no Save button. The tab is now called Administration.

  • Global integrations. A Jira admin connects an integration once for the whole site under App Settings > Global Integrations, so users do not connect it themselves. Available are Microsoft 365 (Outlook) and Tempo Timesheet & Tempo Planner. Slack and Google Workspace followed in later updates.

  • Customers view. Jira admins and Out of Office Admins can switch Team Availability from Users to Customers and manage out of office rules for Jira Service Management customers. The switch appears once an admin turns on Allow customers to have out of office rules in App Settings > General Settings > Service Management.

What changed or was removed

  • Out of Office administration is inside the app, on the App Settings tab, now called Administration. It is no longer in the Jira administration area.

  • The entry point in your Jira profile is gone. Forge does not offer it.

  • The entry point inside a space is not available at the moment. It is coming back soon.

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

  • All tabs were renamed. Migrating from Connect to Forge lists the old and new names.

What you need to do

  • JQL search aliases: a saved filter, board card colour rule or dashboard gadget that uses a dotted alias such as outofoffice.today returns no one; change it to outofoffice-today. See Migrating from Connect to Forge.

  • Space admins' spaces: reselect them in Administration > Permissions. See Migrating from Connect to Forge.

  • Legacy REST API tokens: replace them before 31 December 2026 and switch your integrations to the new base URL. See Migrating from Connect to Forge.

  • Customer groups: if customers with an Atlassian account need out of office rules, choose their groups under Customers in Administration > General Settings > Service Management. Portal-only customers are carried over from the Connect setting. See Migrating from Connect to Forge.