Migration to Forge: What’s Changing in JWT for Jira Cloud?

As part of Atlassian’s shift away from the Connect framework, Jira Workflow Toolbox Cloud is migrating to Forge, Atlassian’s modern and more secure cloud app platform. This is a fundamental architectural evolution with important implications for how updates and functionality work going forward.

Why This Matters

Forge changes the underlying architecture of our app by:

  • Hosting modules directly on Atlassian’s infrastructure

  • Enabling stronger data residency, compliance, and security

  • Allowing future integration with Atlassian’s platform capabilities natively

Our current release includes the first set of Forge-based modules, and we will continue migrating more modules gradually in future versions.

Impact on You: Manual Update Required

Unlike previous releases, where updates were automatically rolled out, major releases, including Forge modules, require Jira admins to trigger the update manually.

To update:

  1. Navigate to Jira Administration > Manage Apps

  2. Find Jira Workflow Toolbox (Cloud)

  3. Click “Update”

How to Stay Informed

To avoid missing future major updates:

Forge FAQs

Why are you migrating to Forge now?
With the Connect framework being deprecated, Forge is the only supported path forward—and offers numerous technical and compliance benefits.

Will this affect performance or stability?
No negative impact is expected. In fact, Forge-hosted modules benefit from Atlassian’s own infrastructure.

Do I need to reconfigure anything after updating?
No reconfiguration is needed. Your current settings, rules, and automations will continue to work as before.


Need help? Contact our team or upgrade to JWT Advanced Edition for personal support sessions.