Documentation for JIRA 4.1. Documentation for other versions of JIRA is available too.

When upgrading JIRA by the 'alternative method', one points the new JIRA installation at the old JIRA database. JIRA will automatically make any structural database modifications required to support new JIRA features.

安全のために JIRA はまず、アップグレード実行直前にデータの XML バックアップ を作成しようとします。これにより、何か問題が生じた場合、アップグレード前のバージョンに『ロールバック』 することが可能になります。

Sometimes the automatic XML backup procedure fails, often because of characters in the database that cannot be represented in XML (typically non-displayable control characters that have been cut-and-pasted in).

In these circumstances, you can force the upgrade to proceed by editing atlassian-jira/WEB-INF/classes/jira-application.properties, and setting jira.autoexport=false.

Once you have upgraded JIRA, successfully, it is best to remove this parameter, as it is no longer needed.

If you have any upgrade problems not covered here or in the upgrade documentation, please contact us — we're happy to help.



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.