Major update - App platform migration
What is changing?
JEMH Cloud is moving to Atlassian’s new app platform. This is a major update, so Jira administrators will need to manually upgrade the app via manage apps.
All of your app configuration data will be preserved, however from Sep 30, 2025 we will no longer store Atlassian API tokens on our own servers.
What do I need to do?
You will need to manually upgrade the app.
If you are using the Workarounds feature and have set an Atlassian API token:
Upgrade date | What you need to do |
|---|---|
Before Sep 30, 2025 | No action needed. The token will be automatically migrated to Atlassian servers. |
From Sep 30, 2025 | Re-add the API token via the JEMH Cloud UI so the token can be stored in Atlassian servers. Failure to do so may result in app features that rely on the API token not working as expected. |
If you are using Automation rules involving the JEMHC app user
As part of this upgrade, the App user has been updated. Due to this, you may see a new JEMHC app user.
Any automation rules pointing to the original JEMHC account should be replaced with the new JEMHC app user.
You can use the JEMHCloud > Tools > User Finder page to help identify the JEMHC app user, along with its respective ID.
For context, the old App user account ID is 557058:1aad7a42-0087-42dc-9dda-6674a94917d9 , and the new App user account ID is 712020:d9b51108-7379-4750-9cce-5d230ead2c0f.
How to upgrade?
Steps on how to perform the upgrade can be found here: Upgrading JEMHCloud major versions.
If you have any queries or issues during the upgrade process, you can reach out to us through our support channels, or email support@thepluginpeople.com.