Migrating from Connect to Forge
Out of Office Assistant now runs on Atlassian Forge instead of Atlassian Connect. Your configuration moves across on its own. Two things need an administrator afterwards: the JQL search aliases, which change form, and your space admins' spaces, which must be reselected. REST API tokens are not copied across, though integrations built against the Connect app keep working.
Start the upgrade
A Jira administrator starts it, and the app does everything else. Once the Forge version is available for your site, open Connected apps in Atlassian Administration, find Out of Office Assistant and select Update. Inside Jira, Apps > Manage your apps leads to the same screen.
There is nothing to prepare beforehand and nothing to import afterwards. Rules keep running while it happens, and the app keeps the same Marketplace listing, so this is an upgrade rather than a new installation.
If the upgrade does not complete, or something is missing once it has, raise a ticket at resolution.de/go/support and name your site address. The app's Support tab reaches the same place through Contact us under Need Help?. Do not uninstall and reinstall the app to try to clear it; that is not how the migration is re-run.
What the upgrade does on its own
The data migration runs when the Forge app is installed or upgraded; there is no import step to trigger by hand. 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.
These come across:
Your out of office rules
Your Tempo integration configuration
General settings
REST API tokens do not; see below. An existing Slack connection keeps working without being reconnected: Slack events still sent to the Connect app are forwarded to the Forge app and handled there.
Update your JQL search aliases
Forge does not allow dots in search aliases, so every alias the app provides now uses hyphens. A saved filter written with the old dotted name no longer resolves and has to be edited.
Nothing warns you about a stale filter: a board or dashboard gadget built on a dotted alias simply stops returning the people who are out of office.
Connect alias | Forge alias |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
Each alias returns what it always did. To fix the affected queries:
Search saved filters, board card colour rules, dashboard gadgets and automation rules for the text
outofoffice.Replace each dotted name with the hyphenated name from the table, then save.
Run each edited query once and confirm it returns the people you expect.
REST API tokens
The new Forge App accepts REST requests on the new URL https://out-of-office.resolution-cloud.com/rest/1.0/.
Existing REST API tokens keep working after the migration but expire on 01.01.2027.
Requests using these legacy tokens are forwarded from the old REST base URL https://out-of-office-connect.herokuapp.com/rest/1.0/, newly created tokens must use the new URL https://out-of-office.resolution-cloud.com/rest/1.0/
Global Integrations
This new release introduces the concept of Global Integrations. Global Integrations are configured centrally by the Jira admin and don’t need authorization by individual users.
Tempo
The Tempo integration setup has moved to Global Integrations under App settings:
Once set up and saved, it appears under My Integrations for all users where they can customize the template mapping:
Microsoft 365 / Outlook
The Outlook Integration is now available as a Global Integration. After being authorized for a M365-tenant, all users with the configured email domains have a default confiugration that creates rules when they enable their Outlook auto-replies without further interaction.
Slack Integration
The Slack integration has changed from the Connect app. The configuration previously done on Slack now moved to Jira.
The confiugration works similarly to the other integrations. You can map templates to the different Slack status emojis, and the rules will be created and removed when the Slack status changes.
Apart from the standard emojis for “Sick” and “Vacation”, you can map any other state to any emoji of your choosing to create rules.
Zapier integration is no longer available
The Zapier integration has been discontinued.
Reselect the spaces your space admins cover
Space admin delegation must name specific spaces; the Connect version's all projects option is gone. A migrated instance prompts you in App Settings > Permissions to reselect them; a space admin can create or change rules and personal templates only inside the spaces named there.
The right to manage other people's rules no longer follows Jira administration rights. Space Admins and Out of Office Admins are both appointed in App Settings > Permissions. Jira admins keep full access without being appointed.
The full model is on Permissions and Access Requirements.
Where the screens moved
Every tab was renamed, so Connect-era instructions will not match the app.
Connect version | Forge version |
|---|---|
User view | Team Availability |
Rules | My Rules |
Templates Library | My Templates. The library is now a picker inside an integration, under Add template from library |
Integrations | My Integrations |
Settings | App Settings, divided into General Settings, Permissions, Global Integrations and Rest API Permissions |
Customer Support | Support |
The separate administration screen | Gone. Site-wide configuration sits under App Settings; other people's rules are managed from Team Availability |
Rules are scoped by Spaces now rather than projects, following Jira's wording. Interface Tour and Navigation Guide walks through the rebuilt screens.
Check these after your instance is upgraded
In My Rules, confirm your rules carry the dates, scope and coverers you expect.
In My Integrations, reconnect anything that no longer shows as connected.
Edit every query that used a dotted search alias.
In App Settings > Permissions, reselect each space admin's spaces and check both admin lists.