As part of our ongoing migration to Atlassian Forge, Classic Exalate for Jira Cloud now runs on Forge infrastructure. Because this update doesn’t change the app’s functionality, configuration, or permissions, Atlassian rolls it out automatically — for most customers there’s nothing to do, and the change is invisible in day-to-day use.
A full native Forge version is planned for a future release.
Does this mean that the updates will now be actioned by the “Exalate for Jira (Forge Extension)” or still the “Exalate” user? Does that mean we need to edit our Permission Schemes in Jira to ensure we allow the new user to make edits?
Hi Hannah,
Happy to clarify both points:
On the acting user: the updates will now be actioned under the Forge-based app’s display name rather than the previous “Exalate” user. So the name you see will change.
On your Permission Schemes: no changes are needed on your side. The app’s user is already registered with the necessary permissions as part of the Forge installation, so it will continue making edits exactly as before — nothing to update.
In short, the only difference is the name shown; your configuration and permissions are unaffected.
Please reach out if anything else comes up.