> For the complete documentation index, see [llms.txt](https://docs.toolsplus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toolsplus.io/atlassian-cloud/intercom-for-jira/forge-migration.md).

# Forge migration

{% hint style="warning" %}
**Action required: Update Intercom for Jira to version 6.0.0 or higher before 31 January 2027**
{% 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 let existing Connect-based apps migrate to Forge, and it requires these apps to migrate by the end of January 2027, when the Connect framework reaches end of support.

## What you need to know

ToolsPlus is migrating Intercom for Jira to Forge in two steps:

1. **Version 3.0.0 (released 10 March 2026)** moved the app onto the Forge platform. The app itself kept running on ToolsPlus infrastructure, which Forge calls a "remote".
2. **Version 6.0.0 (released 20 October 2026)** moves the app's features and data onto Atlassian-hosted Forge infrastructure. Version 6.0.0 or higher is the recommended version going forward.

**The app experience remains largely the same.** The one change Jira users notice is that [linking conversations on the work item view requires edit permission for the work item](#linking-requires-permission-to-edit-the-work-item).

For details on all Forge versions, please refer to the [Changelog](https://docs.toolsplus.io/atlassian-cloud/intercom-for-jira/changelog.md).

### **Potential impact**

From February 2027, ToolsPlus will begin to shut down the ToolsPlus-hosted service that the Connect versions (1.x and 2.x) and the first Forge versions (3.x to 5.x) depend on. **These versions will stop working then. As long as you update to version 6.0.0 or higher before 31 January 2027, 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.

No further steps or data migration is required.

## Changes in detail

This change is invisible to all app users. You can find the full list of changes on the [Changelog](https://docs.toolsplus.io/atlassian-cloud/intercom-for-jira/changelog.md) page. Below we briefly explain the changes most relevant for the migration:

### New app architecture

The Atlassian Connect app consists of an app hosted on ToolsPlus' infrastructure.&#x20;

**Versions 3.x to 5.x** turned that app into a Forge Remote: Jira loads the app's screens through Forge, but every request, notification, and Intercom API call is still processed by ToolsPlus infrastructure, and Intercom connections are stored there.

<figure><img src="https://3976155500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LGUXywqOAgHcx2c0YGM%2Fuploads%2FGc2Qqc3zxMSm6rLBhuee%2FArchitecture3-5.png?alt=media&amp;token=c6632156-ce64-4585-aa45-1d976b2d35a9" alt=""><figcaption><p>Intercom for Jira 3.x to 5.x: Forge app backed by ToolsPlus-hosted Remote</p></figcaption></figure>

**Version 6.x** runs the app's features on Atlassian-hosted Forge compute, stores data in Forge storage, and calls the Intercom API directly from Forge. A tiny bit of stateless ToolsPlus infrastructure is still required to help with Intercom authorization when you connect a Jira space. The Remote service keeps a small set of installation housekeeping tasks until the ToolsPlus-hosted service shuts down after January 2027.

<figure><img src="https://3976155500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LGUXywqOAgHcx2c0YGM%2Fuploads%2FlczjxXloOHOk3XbFuMu0%2FArchitecture6.png?alt=media&amp;token=6af94571-48af-42b6-9485-2c69532b9068" alt=""><figcaption><p>Intercom for Jira 6.x: features and data on Atlassian-hosted Forge infrastructure</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 were previously included in the two broad Connect scopes. While it may look like we expanded the set of scopes, **the app gets a narrower, more clearly defined set.**

The *read:app-system-token* scope allows the ToolsPlus-hosted Remote app to communicate with the Forge platform and make Jira API calls (this scope will go away after January 2027). The *storage:app* scope lets the app use Forge-provided storage.

Version 6.0.0 requests no new scopes, but it tightens permissions and makes them more explicit, such as the external addresses the app contacts.

### Linking requires permission to edit the work item

From version 6.0.0, linking and unlinking Intercom conversations on the work item view requires the **Edit work items** permission on the work item. Earlier versions let anyone who could view the work item link and unlink conversations. Users without the permission still see the linked conversations, but they can't perform the **Link** or **Unlink** actions. If users who only view work items need to link conversations, grant them **Edit work items** in the space's permission scheme.

### New uninstall and reinstall behavior

Before version 3.0.0, Intercom for Jira could be uninstalled and reinstalled without breaking the existing setup. Starting with version 3.0.0, if an admin uninstalls and then reinstalls Intercom for Jira, the Intercom connection 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). 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**. A message will inform 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?

Conversation links, space settings, and notification settings stay in Jira, as before. From version 6.0.0, your Intercom connections move from ToolsPlus-hosted storage to Forge storage on Atlassian infrastructure. The move happens automatically after the update, and ToolsPlus deletes its copy once it completes. See [Changelog](https://docs.toolsplus.io/atlassian-cloud/intercom-for-jira/changelog.md).

## Questions

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