...
Remove redundant data from the tables AO_242870_REVISION_HISTORY and AO_242870_ISSUE_REVISION.
Exclude issues with entries in baselines, to retain baseline information.
Execute the cleanup as a background job which cannot be aborted once executed.
Other important things
...
Once executed, the cleanup process may take several hours to finish depending on the amount of data you have.
Our baseline tests with 25 million revision data finished processing between 6 to 8 hours. The process runs in the background and you can still proceed to work in R4J. However, we suggest proper planning and scheduling execution outside business hours.
R4J 4.5 has been verified on Jira 7.13.x to Jira 8.18.x on the following database types and versions:
SQL Server 2014 and 2016
postgresql-11.11-2
Oracle 19c
MySQL 5.7.33
R4J 4.5 revision data is not compatible with older versions of R4J as stated in our release notes.
Check out the Summary of functions affected by revisions restructure in R4J 4.5
| Note |
|---|
We highly recommend to backup your data, make necessary preparations before performing the process, and first run and verify the result on a test/staging system. If you encounter issues with R4J 4.5, please reach out to us through our support portal. |
Cleaning up
To perform the cleanup process:
...