How to update the Issue History for Jira?
We have significantly enhanced the Issue History for Jira app, providing many new options that improve its security and functionality. As a result, you will need to manually update to the latest version of the app.
The app update is required because it is migrating to the Atlassian Forge platform, which offers enhanced security and reliability. We also plan to transition to Runs on Atlassian, meaning the add-on and all databases and information will be hosted and operated exclusively on Atlassian resources. There will be no changes to the app’s functionality for users.
Important: You need to have admin rights to run updates for Jira Cloud.
How to make the necessary updates?
You must have Jira admin rights to update the app to the latest version. If you don't have such rights, please contact your admin.
To update the app, please follow these steps:
Step 1: Go to Apps and choose Manage apps.
Step 2: In the list of your installed apps, find Issue History for Jira. You will see the notification that an update is available. Click Update button.
If you have the latest version of the app, there will be no Update button and no "Update available" message.
In the app's details, you will see your current version of the app.
What steps to take if the update isn’t completing and the page shows an endless loading spinner?
It may take some time for the update to be applied across all clients. Try refreshing the page and attempting the process again.
What to do if a saved link to Issue History stops working after the update?
That means that you are using an outdated link format. You need to launch the Issue History add-on from its new initial location: Apps → Issue History.
If you need help or want to ask questions, please contact SaaSJet Support or email us at support@saasjet.atlassian.net.
Haven’t worked with the add-on yet? Give it a try