How to update the Issue History for Jira?

We have significantly enhanced the Issue History for Jira add-on, 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 add-on.

The add-on 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 add-on’s functionality for users.

Important: You need to have admin rights to run updates for Jira Cloud.

How to make the necessary updates?

1. Activate the Issue History for Jira add-on to view the “Update message.”

2. The update message will be visible.  

3. Click on the “do it yourself” link.

4. Click the “Update” button located in the row for the Issue History add-on.

5. To start the manual update, click the “Accept & update” button.

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 ⬇