Major update - New scopes for Workarounds user support

Summary

Workarounds user API token authentication is being deprecated by Dec 31, 2025. We are aware of the tight deadline here, it is something that has been mandated on us by Atlassian, the path to addressing this is not a single change. Sorry if this causes confusion or impact. We are in touch with Atlassian and have asked for an extension but, still, have no response.

A new major version of JEMHC has been deployed including new scopes to allow the JEMHCloud app to perform user impersonation requests, replacing the old API token authentication.

You must upgrade prior to Dec 31, 2025 if you are using the Workarounds feature (auto create users, user group lookup, group membership lookup affecting notifications, group custom fields etc)

What is changing?

Atlassian compliance changes mean that Workarounds can no longer be authenticated using user supplied API tokens. Instead, they must be authenticated using Forge user impersonation.

After the Dec 31, 2025 deadline, any customers that have not upgraded will no longer be able to use Workarounds with API token authentication. The app must be upgraded make Workarounds feature work with the new authentication.

Am I affected?

Customers relying on the Workarounds feature must upgrade by Dec 31, 2025. Failure to upgrade will result in the API token authentication no longer working, resulting in behaviour changes and losing access to features performed by the Workarounds user.

As more Connect functionality is being phased out in replacement of Forge, we encourage customers to upgrade even if they do not use the Workarounds feature.

Next steps

See Upgrade the app to the latest major version for next steps and complete upgrade (that add new scopes required) by Dec 31, 2025.