Atlassian is retiring the framework the current Realm app is built on (Atlassian Connect) on January 31, 2027. Realm has released a new version of the app built on Atlassian’s successor framework (Forge). Every Jira and Confluence connection made through the Atlassian Marketplace app needs to move to the new version before that date.
The migration has two parts that belong together:
- An Atlassian admin accepts the app upgrade on your Atlassian site.
- A Realm admin reconnects the data source in Realm using the new Installation ID.
Syncing stops as soon as the upgrade is accepted in Atlassian and resumes after the reconnect in Realm. Plan to do both parts in one sitting.
Who needs to do this
Only connections made through the Realm app on the Atlassian Marketplace (Jira Cloud and Confluence Cloud). Connections that use a Personal Access Token (Jira or Confluence Data Center) are not affected.
Step 1: Accept the upgrade in Atlassian
In your Jira or Confluence site, go to Settings > Apps > Manage apps, find the Realm app, and accept the new version. Atlassian asks an admin to approve it because the app’s permissions change: the new version uses Atlassian’s current read permissions for the same content Realm already syncs.
If your site has both Jira and Confluence, one upgrade covers both.
Step 2: Copy the Installation ID
Open the Realm app page in your Atlassian site:
- Jira: Settings > Apps > Realm
- Confluence: Settings > Realm
The page shows an Installation ID. Copy it. If you are not also a Realm admin, send the Installation ID to a Realm admin for the next step.
Step 3: Reconnect in Realm
In Realm, go to Settings > Data sources, open Jira or Confluence, and click Reconnect. Select the Forge app tab, paste the Installation ID, and connect.
Your selected projects and spaces, synced content, and settings stay in place. Syncing resumes with the new authentication.
If you sync both Jira and Confluence from the same Atlassian site, reconnect each data source. The Installation ID is the same for both.
What changes after the upgrade
The new app syncs content as the Realm app user instead of a person’s account. The app user follows Jira’s and Confluence’s normal permission rules, so content that is hidden from it will no longer sync.
Jira
By default Jira grants apps access to every project through the atlassian-addons-project-access project role, which Jira adds to each project’s permission scheme automatically. Content can still be hidden from the app user:
- If that role was removed from a project’s permission scheme, the project’s issues are hidden from the app. Re-add the role to the scheme.
- If an issue security scheme does not include the role, issues under those security levels are hidden. Add the role to the security level.
- App Access Rules (in Atlassian Administration under Security) can block apps from specific projects.
Confluence
- The app user sees unrestricted content in the spaces you select.
- Restricted spaces and restricted pages are hidden from the app user unless you grant it access. A restriction overrides space permissions, so even site admins are excluded unless they are on the restriction list, and the same applies to the app user.
- App Access Rules (in Atlassian Administration under Security) can block apps from specific spaces.
Troubleshooting
Content is missing after the upgrade. Check the permission points above for your product. If Realm could not access a selected project or space, Realm may have deselected it, so after granting access also reselect it on the data source page in Realm.
Syncing stopped and nobody reconnected in Realm. An Atlassian admin may have accepted the upgrade without completing the reconnect. Follow steps 2 and 3 to restore syncing.
Realm reports the installation is already connected. The Installation ID is already attached to another Jira or Confluence data source in your Realm organization. Open that existing data source and reconnect it instead of creating a new one. 
