Upgrading to Automation for Jira 7.3
Automation for Jira 7.3 uses different types of IDs in database tables—
biginteger instead of
integer. If you're upgrading from earlier versions, we'll migrate the IDs to the new type automatically after upgrading, but we need you to complete some prerequisite steps to make it successful. This automatic migration won't work for the MySQL and SQL Server databases, so you'll also need to download and run scripts on your database.
To upgrade to Automation for Jira 7.3:
How to follow these steps?
Steps 1-3 are not required, but we recommend completing them for large Jira instances—they will speed up your upgrade. If your Jira instance is small or you have plenty of time, feel free to start with Step 4: Update Automation for Jira.
Step 1: Stop your Jira instance
Your automation rules need to be disabled, and you'll also be deleting some data from the database in the next step. The easiest way to do it is to just stop your Jira instance.
Step 2. Delete data from database tables
Delete the data from the following Automation for Jira tables in your Jira database. These particular tables might contain a large number of entries, which might slow down the upgrade. They contain entries from your audit log, automation queue, and rule statistics.
Before you begin:
- Make sure to back up your database before deleting data from these tables. For more info, see Backing up data.
- The order in which you delete the data is important. Follow the numbers 1-6 first, and then move to rule statistics (no specific order for rule statistics).
- Script: You can download and use this script to delete the data automatically.
2. AO_589059_AUDIT_ITEM_PROJECT; 3. AO_589059_AUDIT_ITEM_ASC_ITEM; 4. AO_589059_AUDIT_ITEM_CGE_ITEM; 5. AO_589059_AUDIT_ITEM_COMP_CGE 6. AO_589059_AUDIT_ITEM;
AO_589059_RULE_STAT AO_589059_RULE_STAT_ROLLUP_DAY AO_589059_RULE_STAT_ROLLUP_HR AO_589059_RULE_STAT_ROLLUP_MIN
Step 3. Start Jira
You can now start your Jira instance.
Step 4: Update Automation for Jira
- Go to Administration > Manage apps > Manage apps.
- Find the Automation for Jira app and click Update. It will be updated to the latest version.
Step 5. For MySQL and SQL Server databases, download and run the scripts
These databases require some extra steps, like changing the foreign keys and indexes. That's why we can't migrate the IDs automatically.
- Stop your Jira instance.
Download one of the following scripts and run it on your database.
For SQL Server, you'll need to replace the "jiraschema" name used in the script with the name of your database schema.
Once completed, start Jira again.
Performance issues on PostgreSQL
We’ve noticed that instances with a large number of entries in the audit log might encounter performance issues after upgrading. This issue occurs only on PostgreSQL databases. If you’ve upgraded and your rules seem to run slower than usual, see Changing the join strategy to improve performance.