> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/email-this-issue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/email-this-issue/forge-migration-guide.md).

# Forge Migration Guide

Atlassian is transitioning all Cloud apps from the older Connect framework to its newer platform, Forge. This is a platform-wide change that affects all Atlassian Marketplace vendors. We are actively preparing Email This Issue (JETI) for this transition and want to keep you informed about where things stand.

Our priorities throughout this migration are customer continuity, data safety, and functional compatibility. We are not rushing a wholesale rewrite — instead, we are taking a deliberate, capability-by-capability approach to ensure that JETI's behaviour after migration remains correct, reliable, and consistent with what customers rely on today. The foundational layer of the migration is now complete, and UI migration components are actively in development, testing, and code review.

This page is the authoritative source for our migration status. It will be updated as milestones are reached and as Atlassian resolves relevant platform dependencies.

### 1. What is changing? <a href="#id-1.-what-is-changing" id="id-1.-what-is-changing"></a>

Atlassian Connect is the framework on which many Marketplace apps — including JETI — have been built since early Cloud. Forge is Atlassian's newer Cloud app development platform, which offers better security isolation, a more modern runtime, and tighter integration with Atlassian's Cloud infrastructure. Atlassian has announced that Connect will reach End of Support in December 2026, and vendors are expected to migrate their apps to Forge before that deadline.

As part of this transition, Atlassian may display admin-facing notices in your Jira or JSM settings for apps that still operate on Connect or on a hybrid Connect/Forge architecture. These notices are informational — they do not mean JETI has stopped working or that your data is at risk. They are designed to direct admins toward the vendor's migration information, which is exactly what this page provides.

### 2. Our migration approach <a href="#id-2.-our-migration-approach" id="id-2.-our-migration-approach"></a>

We are migrating JETI to Forge in a structured, phased way. Rather than treating the migration as a single risky rewrite, we are mapping each of JETI's capabilities to the equivalent Forge architecture, assessing readiness, and migrating components in order of stability and Atlassian platform support. Our guiding principles are:

* Migrate carefully, not quickly — customer continuity takes priority over speed.
* Assess each capability individually and map it to Forge-compatible architecture before migrating it.
* Follow Atlassian's official Connect-to-Forge migration guidance and adapt as that guidance evolves.
* Migrate areas where Forge already provides the required platform capabilities; track and defer areas where Atlassian platform gaps remain.
* Avoid making assumptions that could introduce permission regressions, workflow disruptions, or inconsistent behaviour.

This phased approach is yielding results: the foundational layer of the migration is now complete, and multiple UI components are progressing through development and testing simultaneously.

### 3. Current progress <a href="#id-3.-current-progress" id="id-3.-current-progress"></a>

| Area                                                               | Status                                           | Notes                                                                                                                                                                                                                                                 |
| ------------------------------------------------------------------ | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Forge adoption / architecture planning                             | Complete                                         | Foundational Forge capabilities are complete: the app is integrated with the Forge platform, with secure data storage, external service communication, and file upload support all implemented and validated. The phased release plan is established. |
| Core module (initial Forge module)                                 | Complete                                         | Initial Forge module is complete. The OAuth2 authorization flow is currently in manual testing.                                                                                                                                                       |
| Admin UI migration                                                 | In Progress                                      | Active development under way.                                                                                                                                                                                                                         |
| Email feature UI (manual email, email tab, workflow post-function) | In Progress                                      | Active progress across all three components: Issue Emails Tab is in manual testing; Workflow Post Function UI is in code review; Manual Email Screen is actively in development.                                                                      |
| Jira event and lifecycle event handling                            | Planned                                          | Scheduled for a later phase of the migration programme.                                                                                                                                                                                               |
| Backend communication layer                                        | Planned                                          | Higher-complexity area with additional development runway in the plan. Work begins in parallel with other phases.                                                                                                                                     |
| JSM portal-user permission handling                                | Blocked — awaiting Atlassian platform capability | Dependent on resolution of [FRGE-971](https://ecosystem.atlassian.net/browse/FRGE-971). See Section 4 below.                                                                                                                                          |

### 4. Known blocker: FRGE-971 <a href="#id-4.-known-blocker-frge-971" id="id-4.-known-blocker-frge-971"></a>

One area of our migration is currently blocked by a platform-side limitation in Forge, tracked in the public Atlassian ecosystem issue [FRGE-971: asUser API requests for JSM portal only (customer account) users](https://ecosystem.atlassian.net/browse/FRGE-971).

In certain JSM workflows, JETI needs to act on behalf of a portal user — a customer account that exists in the JSM portal but is not a full Atlassian Cloud user. Today, under Connect, this is handled through a mechanism that correctly respects the portal user's identity and permissions. In Forge, the equivalent capability — `asUser()` API requests scoped to JSM portal/customer account users — is not yet fully supported by the platform.

This matters because migrating JSM portal-user scenarios to Forge prematurely, without this capability in place, could result in permission handling that differs from current behaviour — potentially affecting workflows that customers rely on. We treat this as a migration blocker for the affected scenarios: we will not migrate those areas until the Atlassian platform capability is available.

Atlassian has acknowledged the importance of this area and has indicated that work is planned or in progress on user impersonation and JSM user management within Forge. We are monitoring the issue actively and will update this page when the situation changes.

Importantly, this blocker does not halt the overall migration. Active development is progressing across all other areas of JETI in parallel. This is a known ecosystem-level dependency, and we are managing it accordingly.

### 5. What this means for you as a customer <a href="#id-5.-what-this-means-for-you-as-a-customer" id="id-5.-what-this-means-for-you-as-a-customer"></a>

**No immediate action is required.** JETI continues to function normally on Connect while our Forge migration proceeds. You do not need to reinstall, reconfigure, or take any steps at this stage.

If you see an admin notice about Connect in your environment, this page is your source of information. The notice describes Atlassian's platform-wide transition; it does not indicate a JETI outage or data risk.

When Atlassian resolves the FRGE-971 platform gap, we will complete the migration of JSM portal-user scenarios. Our goal is that the Forge migration is entirely transparent to customers: those relying on portal-user workflows will not experience any functional change.

If you would like to help Atlassian understand the business priority of this platform capability, you may vote for or watch the [FRGE-971 Atlassian ecosystem ticket](https://ecosystem.atlassian.net/browse/FRGE-971). This signals customer impact to Atlassian's product team and is entirely optional.

### 6. Frequently asked questions <a href="#id-6.-frequently-asked-questions" id="id-6.-frequently-asked-questions"></a>

Does this mean JETI will stop working?Why has the migration not been completed yet?What is Forge?Why am I seeing an Atlassian notice about JETI?Do we need to reinstall or reconfigure JETI?How can we follow progress?

### 7. Next updates <a href="#id-7.-next-updates" id="id-7.-next-updates"></a>

The near-term migration trajectory, and what to expect in upcoming updates to this page:

* Completion of UI components currently in testing and code review (Issue Emails Tab, Workflow Post Function UI) and progression of the Manual Email Screen toward testing
* Further Forge migration milestone completions, by capability area, as development advances
* Updates on FRGE-971 and Atlassian's resolution of the JSM portal-user capability gap
* Any required customer action, if applicable — communicated with clear advance notice