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.
Our goal is a gradual and safe migration and we currently aim for completion by the end of October 2026, with some buffer time before the End of Connect support at the end of January 2027. We are not replacing everything at once. Instead, we are moving modules in stages so we can deliver improvements continuously while guaranteing the app stays usable and stable. Our goal is for you - our customers - to not even notice the difference most of the time.
The forge migration runs in parallel to usual app maintenance, improvements and continuos new feature development.
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
Impact on You: Manual Update Required
For most customers, no configuration changes are required, but all app updates including new Forge modules require a manual update.
There is a single exception:
Due to stricter Forge Authentication rules, any normal user selected in a “Run as” Section of any workflow function must have logged in at least once. The JWT App user can be used independent of this. If you are using some kind of technical user that can’t log in even once, you’ll have to replace that user in the workflow.
Manual Updates Required
Unlike most releases, where updates are rolled out automatically, major releases that include Forge modules require Jira admins to manually trigger the update. This is due to how the Atlassian Marketplace handles mixed Connect+Forge apps.
To update:
-
Navigate to Jira Administration > Manage Apps
-
Find Jira Workflow Toolbox (Cloud)
-
Click “Update”
How to Stay Informed
To avoid missing future major updates:
-
Click “Watch app” on the JWT Cloud Marketplace listing
Edit Restrictions for Space admins
At the moment, only Jira admins can edit JWT workflow rules. The “Edit workflow” permission, that allows space admins to edit isolated workflows in their spaces does not extend to any Forge workflow rules. This is an open work item at Atlassian - if this affects your team, please consider voting on it to increase it’s priority.
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?
For most customers, no reconfiguration is needed. The current settings, rules, and automations will continue to work as before with a single exception:
Due to stricter Forge Authentication rules, any normal user selected in a “Run as” Section of any workflow function must have logged in at least once. The JWT App user is unaffected.
Does this affect existing customers?
Yes, but mostly in a positive architectural sense. We’ll improve the technical foundation while keeping JWT Cloud supported and stable throughout the transition.
The only new restrictions is that editing Forge workflows functions are currently restricted to Jira admins (s. above).
Does this affect DC-to-cloud migrations?e
No impact is expected. After our migration has moved to Forge you will need to update both your DC and your Cloud version of the App to the newest version, which is always advised anyway for the the smoothest migration experience.
Is JWT Cloud already fully migrated to Forge?
No. The migration is ongoing and is being delivered gradually. Some modules and post functieons have already been migrated, and more will follow in future releases. Refer to the table below for details.
Will all functionality move at the same time?
No. We are migrating step by step. This reduces risk, allows continuous delivery, and helps us validate the architecture with real customer scenarios.
Does this mean a pause on new features?
No, we are continuously improving JWTC and delivering new features side-by-side with our Forge transformation. The latest example is our AI feature helping you create custom expressions.
Overview Forge migration progress
The following table provides an overview of all app features and their current status.
|
Feature category |
Forge |
Connect |
|---|---|---|
|
Conditions & Validators |
Logical Validator Fields required |
Compare two values Jira expression |
|
Post functions |
Add comment Add or remove watchers Create Issue Execute Remote Action Execute Sequence of Actions Send email Transition Issue Update Fields Update linked issues |
|
|
Admin pages |
Get Started page Audit Log Remote Actions Expression Test Page |
Migration Log |
|
Miscellaneuos |
Expression Editor AI Expansion |
DC-Cloud-Migration |
How we prioritize what comes next
When deciding which post functions to migrate next, we generally look at a combination of factors:
-
Customer usage and demand
-
Technical complexity and architectural dependencies
-
Reusability of components for other workflow functions
-
Risk reduction for the broader Forge transition
This helps us balance fast impact with the more complex functions that need additional groundwork.
Need help? Contact our team or upgrade to JWT Advanced Edition for personal support sessions.