Page tree
Skip to end of metadata
Go to start of metadata


This page describes how to upgrade JIRA 4.4.x or later in a way that allows you to safely roll back to your previous system if the upgrade process takes longer than expected or if you encounter issues. This method is especially useful for enterprise environments and for organisations where JIRA is mission-critical for the business. You can also use this method so you have a fallback option if you are performing a complex system change, such as changing the operating system that will run JIRA, the database that will store JIRA's data or the location of JIRA's index and/or attachments paths.

Because this process is designed to provide the safest possible upgrade method, it requires advanced knowledge of database administration tasks. We recommend you have the following resources and/or skill sets available for your upgrade:

  • Database Administrator - for general production-level database administration (i.e. run backups, create, remove, restore, etc.)
  • JIRA Application Administrator - for general application administration and upgrade managment (i.e. JIRA SME, user with System Administrator privileges and deep understanding of application and associated dependencies within your organization.)
  • Systems/Network Administrator - for managing systems and networks (i.e. proxy servers, DNS changes, monitoring, VM's, hardware, etc.)

This upgrade process also requires you to make backups of your database, which can be time-consuming. Customers with large JIRA environments should plan for four hours of downtime. If you know your system takes several hours to re-index, you might want to allocate more than four hours for the upgrade.

This graphic illustrates the process described in this document. For simplicity, the illustration shows how you can perform an upgrade using two different pieces of hardware. However, you can just as easily install JIRA in different directories on the same server to test and perform an upgrade. In this case, simply ensure that you use separate installation and database directories during the testing.


시작하기 전에

  • Read about the new version - Review the release notes and upgrade notes for the version of JIRA that you are upgrading to. See Production Releases. If you plan to skip a few JIRA versions during your upgrade, we strongly recommend that you read the upgrade guides for all major versions between your current version and the version to which you are upgrading. Refer to Important Version-Specific Upgrade Notes for quick links to these guides.
  • Check your license - Verify that your license support period is still valid.
  • Check for known issues - Use the JIRA Knowledge Base to search for any issues in the new version that will affect you.
  • Check for compatibility:
    • Confirm that your operating system, database, other applicable platforms and hardware still comply with the requirements for JIRA 7.1. The End of Support Announcements for JIRA page also has important information regarding platform support for future versions of JIRA.
    • If you have installed JIRA plugins (i.e. not included with JIRA), verify that they will be compatible with the version of JIRA you are upgrading to. You can find a plugin's compatibility information from the the plugin's home page on the Atlassian Plugin Exchange.

Some anti-virus or other Internet security tools may interfere with the JIRA upgrade process and prevent the process from completing successfully. If you experience or anticipate experiencing such an issue with your anti-virus/Internet security tool, disable this tool first before proceeding with the JIRA upgrade.


If you have any problems during the upgrade process, create an issue at our support site so that we can help you resolve the problems with your upgrade. We strongly recommend that you perform the below procedure first as a test only. This will allow you to note any complications (e.g. with customized settings or add-ons) ahead of time so that you can minimize the downtime of the system.

1. 업그레이드를 위한 준비

When you begin preparing to upgrade, it's best practice to halt any major changes to your production system (such as plugin upgrades, customisations, etc.). Keeping your production system as stable as possible will make testing the upgrade version simpler.

It's also a good idea to let your users know about planned downtime, either through email or by using JIRA's announcement banner.

2. 프록시 서버 셋업

Before begining the upgrade process set up a reverse proxy, such as a load balancer. The proxy server allows you to redirect users to a different JIRA server without having to wait for a DNS change - this change will be invisible to the end-user.  If, at any point during the upgrade process, you encounter issues you can't resolve and you need to rollback to your existing JIRA instance, simply restart your existing JIRA instance and reconfigure the proxy server to point to the old server.

If you use mointoring, API calls (such as SOAP, REST, or CLI), or scripts associated with your production server, update them with the new proxy information.

Please see the following documentation for further information on configuring Apache:

3. 준비단계 및 JIRA 새버전 테스트

  1. If you want to use a copy of your production data when you test the upgraded JIRA system, make a copy of your production database using your native database backup tools. See Backing Up Data. You can alternatively skip this step and use a new database for testing.
  2. Install the version of JIRA you want to upgrade to onto a system you can use for testing (use either a test server or a separate directory on an exisitng system). This will become your new production system after you complete the upgrade process. Follow the instructions here to install a new version of JIRA: Installing JIRA.

  3. Migrate any customisations you use in your production system. Follow the instructions in step 3.4 (Migrate your existing JIRA configurations over to your new JIRA installation) in the "Migrating JIRA to Another Server" page.
  4. Connect the new version of JIRA to the copy of the production database (not the existing production database) or a new testing database. See Connecting JIRA to a Database.
  5. Start the new version of JIRA. See this Knowledge Base article about how to test mail settings without accidentally sending notifications to users from the test system: How to Prepare a Development Server's Mail Configuration.
  6. Install any plugins that you use in your existing production version of JIRA. Some plugins have different compatibility for different JIRA vesions, so this step will ensure that your plugins are updated for this new JIRA version.
  7. Re-index JIRA  so the new plugin information is captured in the index.
  8. Check out the features and functionality you use in the new version to understand how they behave and how any changes will impact your team. It can be very helpful to have a group of users look at the new system and carry out their usual tasks to make sure they won't run into any issues when the new version is in production.
    When you are ready to begin the process of migrating your production data to this new version, shut down JIRA (for example, by executing either the /bin/ or \bin\stop-jira.bat file in your JIRA Installation Directory, or by stopping the JIRA service).

4. 이전버전 JIRA 사용중지하고 새로운 JIRA 시작

Before disabling your old JIRA production instance, identify the location of your attachments and index directories. If they are located outside of your JIRA Home Directory, you will back them up manually later during the upgrade process. These pages describe how to find out where these directories are located in your environment:

If your attachments and index directories are located outside of the JIRA Home directory, note their location so you can easily find them later.

After you've located the attachments and index directories, disable the old JIRA production instance so you can perform a database backup:

  1. Shut down your old production JIRA instance (for example, by executing either the /bin/ or \bin\stop-jira.bat file in your JIRA Installation Directory, or by stopping the JIRA service).
  2. Using your database's native backup tools, perform a backup of the data in your old production JIRA instance. See Backing Up Data.
  3. Set the newest copy of the production database as the new database for production.


    Make sure that the database set up for the new production version of JIRA is clearly distinguishable from the database backup of your old production JIRA, and that the new production instance is not configured to connect to the old production database.

  4. Synchronise the JIRA attachment directories:
    1. Locate the JIRA Home directory. You can find information about the location of the directory by navigating to the <jira-application-dir>/WEB-INF/classes/ file in your JIRA Installation Directory. Alternatively, you can open the JIRA Configuration Tool to see the directory that is set as your JIRA Home.
    2. Navigate to the directory specified in the configuration file and create a backup of it in another directory.
    3. If the attachments and index directories are located outside of your JIRA Home Directory, you must back them up separately. (See the beginning of this task for information on how to find these files.)

      Also refer to Backing Up Data for more information about backing up attachments in JIRA.

    4. Replace the JIRA Home directory (and the attachment and index directories, if separate from the JIRA Home directory) in the new JIRA production environment with the backups you made of the old production directories.
  5. Start the new version of JIRA in your new production environment. When you start this version, JIRA will upgrade your data and may perform a re-index. When the re-indexing is complete, verify that your data is present and that there are no issues with the system.


9. 업그레이드 후 체크사항 및 작업

새로운 JIRA를 구동한 후에는 다음의 체크사항 및 작업을 수행할 것을 권장합니다.

  1. JIRA가 정상적으로 동작하는 것처럼 보여도, server logs에 에러메시지가 있는지 여부 확인하십시요. 해결할 수 없는 에러가 발생한 경우 로그파일과 함께 https://support.atlassian.com으로 기술지원 요청하십시요.
  2. 이전에 External User Management를 사용하였다면, 새로운 JIRA 에서도 사용설정하십시요.
  3. 업그레이드 하면서 서버하드웨어를 변경하였다면, 인덱스, 첨부, 백업 디렉터리 경로를 JIRA의 관리자 항목에서 확인하고 필요한 경우 변경하십시요.
  4. 테스트 기간동안 메일을 사용중지하였다면, 메일을 사용설정하십시요.
  5. 과거의 JIRA에서 새로운 JIRA로 이전을 한 경우, 테스트가 충분한지 확인하십시요.
    1. 새로운 JIRA에 대한 플러그인을 개발하였다면, 새로운 JIRA 버전으로 다운로드한 JAR 파일을 설치 하시고 플러그인을 위한 다른 요구사항이 있는지 확인하십시요.
    2. 플러그인이 속성파일을 가지고 있다면, 과거의 속성파일의 변경사항을 동일하게 새로운 속성파일에 적용하십시요.
  6.로 로그인
    1. 적절한 라이센스 정보 확인.
    2. Server ID를 새로운 production Server ID로 수정하고 저장.
    3. 새로운 서버에 production 라이센스 업데이트.

Once you have confirmed the availability of compatible versions, you should upgrade your plugins after successfully upgrading JIRA. This can be done via the 'Plugin Repository' in your Administration Console. It is recommended that you re-index JIRA after upgrading your plugins.

Congratulations! You have completed your JIRA migration/upgrade.



  • No labels