Disabling auto-export
Upgrading Jira applications
- Upgrading Jira applications manually
- Upgrading Jira applications with a fallback method
- Upgrading Jira applications using a rapid upgrade method
- Skipping major versions when upgrading Jira applications
- Disabling auto-export
- Rolling back a Jira application upgrade
- Migrating Jira applications to another server
- Establishing staging server environments for Jira applications
On this page
Related content
- No related content found
This document applies only to disabling auto-export during upgrade. For information on configuring scheduled backups, see Automating JIRA Backups.
When upgrading Jira, the new Jira installation points at the old Jira database. Jira will automatically make any structural database modifications required to support new Jira features.
To be safe, Jira first tries to create an XML backup of your data at the point just before the upgrade. This would allow you to 'roll back' to the old Jira version, should anything go wrong.
Sometimes the automatic XML backup procedure fails, often resulting from characters in the database which cannot be represented in XML — such as non-displayable control characters that have been 'cut-and-pasted' into a Jira field.
In these circumstances, you can force the upgrade to proceed by editing your jira-config.properties file (in the Jira home directory) and setting the property jira.autoexport=false
See Making changes to the jira-config.properties file for more information.
After having successfully upgraded Jira, it is best to remove this property (or disable it with a '#') as it should no longer be required.
If you have any upgrade problems not covered here or in the upgrade documentation, please contact us — we're happy to help.
Related content
- No related content found