# Forge migration

{% hint style="warning" %}
**Action required: Update Intercom for Jira to version 3.0.0 or higher**
{% endhint %}

Intercom for Jira is an Atlassian Marketplace app built by ToolsPlus using the Atlassian Connect app framework. In 2019, Atlassian announced a new app framework and platform called [Atlassian Forge](https://developer.atlassian.com/platform/forge/). Since its launch, Atlassian has matured the platform to enable existing Connect-based apps to migrate to Forge, and it requires that these apps migrate by the end of 2026, when the Connect framework reaches end of support.

## What you need to know

In March 2026, ToolsPlus will roll out a major new version, 3.0.0, of Intercom for Jira to the Atlassian Marketplace, which becomes the supported Atlassian Forge app version going forward.

**The app experience remains exactly the same**; for app users, there are minor to no visible changes.

### **Potential impact**

The current Intercom for Jira major versions 1.x.x and 2.x.x will stop working starting in November 2026 as we begin removing Connect app support. **As long as you upgrade to version 3.0.0 or higher before 30 September 2026, we do not expect any impact.**

## What you need to do

1. In the left-hand navigation on your Jira site, open the **Apps context menu (⋯) > Manage apps**. There will be a message informing you that "App management has moved to Administration". Click **Take me there**. This opens the **Connected apps** list for your site.
2. Find **Intercom for Jira** in the list. It will have an **UPDATE** status next to its name.
3. Click **View app details** in the actions column.
4. Select **Update** in the top-right corner of the app details screen to update the app to the latest version.

## Changes in detail

For all app users, this change is invisible. There are minor to no visible changes to the app. The changes are on the platform level, and are as follows:

### New app architecture

The Atlassian Connect app consists of an app hosted on ToolsPlus' infrastructure. With the Forge platform, this changes slightly. The existing app now acts as a "remote" to an Atlassian-hosted platform app that has access to Atlassian-hosted infrastructure.

<figure><img src="/files/hnL0eMZHz9x5SpERBUqO" alt=""><figcaption><p>Intercom for Jira on the Atlassian Connect app framework vs. Forge app platform</p></figcaption></figure>

### New set of scopes

The Connect app (up to version 2.3.0) requested [only two scopes](https://developer.atlassian.com/cloud/jira/software/scopes-for-connect-apps/#scopes-for-atlassian-connect-apps) (permissions):&#x20;

* READ
* PROJECT\_ADMIN

With the new Forge platform, Atlassian broke the broad Connect scopes down into smaller pieces, so starting from version 3.0.0, the app now requires the following [set of scopes](https://developer.atlassian.com/platform/forge/manifest-reference/scopes-forge/):

* read:jira-work
* read:jira-user
* write:jira-work
* manage:jira-project
* manage:jira-configuration
* read:app-system-token
* storage:app

Apart from the last two scopes (*read:app-system-token* and *storage:app*), all the others were previously included in the two broad Connect scopes. While it may look like we expanded the set of scopes in version 3.0.0, **the app now gets a narrower, more clearly defined set.**

Regarding *read:app-system-token* and *storage:app*, these are two new scopes required for the app to function on the Forge platform. The *read:app-system-token* scope allows the Remote app to communicate with the Forge platform and make Jira API calls. The *storage:app* scope allows the app to use the Forge platform-provided storage.

### New uninstall and reinstall behaviour

Before version 3.0.0, Intercom for Jira could be uninstalled and reinstalled without breaking any existing setup. Starting with version 3.0.0, if an admin uninstalls and then reinstalls Intercom for Jira, the connection to Intercom in Jira spaces [must be revoked](https://docs.toolsplus.io/atlassian-cloud/intercom-for-jira/guides/jira-administrators/revoking-intercom-connection) and [reconnected](https://docs.toolsplus.io/atlassian-cloud/intercom-for-jira/guides/jira-administrators/setting-up#connecting-a-jira-space-to-intercom). All other configurations and data, such as conversation links, will remain in place and unaffected by the reinstall.

### Minor improvements

* When Intercom for Jira forwards Jira work item comments to linked Intercom conversations, it now replicates the comment formatting more accurately in the Intercom notes.
* Workflow post functions are now supported in team-managed spaces (projects).

## FAQs

#### Which app version do I currently have installed?

In the left-hand navigation on your Jira site, open the **Apps context menu (⋯) > Manage apps**. There will be a message informing you that "App management has moved to Administration". Click **Take me there**. This opens the **Connected apps** list for your site. Find Intercom for Jira in the list and click **View app details** to see the currently installed app version.

#### What happens to my data?

There is no change. The app continues to store the majority of the data it requires to function on Jira itself and the remaining parts on ToolsPlus-hosted storage. This is exactly the same as before. The only difference is that the "remote" app service is now invoked via the Forge platform rather than the Connect platform.

## Questions

If you have any questions or concerns about this migration, please contact us via your preferred channel at <https://toolsplus.io/support/>.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.toolsplus.io/atlassian-cloud/intercom-for-jira/forge-migration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
