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

  1. You may want to set a banner (see Configuring an Announcement Banner) to warn users that JIRA will be inaccessible/read-only while an upgrade is performed.
  2. There are two ways to ensure that users cannot update your existing JIRA instance:
    • Make JIRA inaccessible: Shut down JIRA, start it on a different port to the one that JIRA usually runs on and do the backup there. Please note, no-one will be able to access JIRA while it is running on a different port during the backup, even to read issues; or,
    • Make JIRA read-only: In your database, remove 'write' permissions from the database user (e.g. jirauser) that JIRA uses. If you do this, users will be able to read issues but will not be able to update them during the backup. For details, please see Making database read-only for upgrade backups.
  3. Leave your existing JIRA inaccessible or read-only until the upgrade is completed successfully.
  • No labels



See our Getting Help page for details.



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.