Upgrade Guide from Jira 7.6 to 7.13

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問


目的

To help provide a detailed guide to help with the upgrade process of large scale and business critical Jira environments to Jira 7.13.latest. Other methods for upgrade also exist, see here: Upgrading Jira application

準備

はじめる前に

  • Check Jira 7.13 Supported Database Versions:
    • Oracle 12c
    • MySQL 5.5, 5.6, 5.7
    • PostgreSQL 9.3 (deprecated), 9.4, 9.5, 9.6
    • Microsoft SQL Server 2012, 2014, 2016
  • Check plugin compatibility
    • Within your current installation of Jira, go to Administration > Add-ons > Manage add-ons. At the bottom of the page, there is a link for Jira update check.

    • Third-party apps may have upgrade requirements, please ensure to be familiar with these requirements as it may require additional intermediate upgrade steps
  • Check other Atlassian product compatibility, see Application links matrix. Jira 7.13 uses AppLinks 5.4.5 - based on that, minimal versions for other applications are:
    • Bamboo 6.6+
    • Confluence 6.8+
    • Crucible/Fisheye 4.4+

    • Bitbucket 5.9+
  • Review the Recommended Readings (links to the right)

Optimize the Upgrade process

These steps will help reduce the amount of time needed for the full upgrade process to complete:

  • Starting Jira 7.9, there is an upgrade task that will migrate Developer Summary data from one table to another as per  JSWSERVER-15748 - Getting issue details... STATUS . This process can take longer when the data in the previous table is very large (1+ million entries). To help reduce the total upgrade time;

    • a manual copy from the old entry of entity_property table can be performed prior 

    • or, apply the workaround to delete anything older than 30 days worth of data as per the bug report

    • or, for Oracle DB, set UNDO Tablespace to autoextend in order to prevent UpgradeTask failure
  • Prepare server.xml to be compatible with Jira 7.13 prior to the upgrade. See Changing server.xml to handle requests with special characters

テスト

We strongly recommend performing your upgrade in a test environment first. Do not upgrade your production Jira server until you are satisfied that your test environment upgrade has been successful. If you have any problems with your test environment upgrade which you cannot resolve, create an issue at our support site so that we can assist you.

Details: Upgrade Checklist and Creating a test environment for Jira.

Upgrade Steps for Jira Software

Before proceeding - third-party apps may have upgrade requirements, please ensure to be familiar with these requirements as additional intermediate upgrade steps may be required.

Upgrading to Jira Software 7.13.latest

  1. Stop the current Jira instance.
  2. Make a copy of the Jira database to a new database.
  3. Make a copy of the Jira_HOME to a new location.
  4. Remove the plugins/ folder located in the new Jira_HOME.
    1. Performing the upgrade without plugins has been found to be more reliable and faster.
    2. If you run Jira Data Center, also remove (and backup) the <Shared>/plugins/ folder.
  5. Modify the dbconfig.xml file in the newly copied Jira_HOME.
    1. Configure the file to point to the newly copied database.
  6. Download Jira Software 7.13.latest Archive version.
  7. Extract your Jira Software 7.13.latest to a new target Jira_INSTALL folder.
  8. Configure your Jira Home folder path and point to the newly copied Jira_HOME.
  9. Copy memory allocation settings and any other custom parameters you deem necessary from the previous installation to the new one, as described in Setting properties and options on startup.

  10. Start Jira and review the logs to ensure the upgrade completes successfully.
  11. If using Service Management, navigate to Cog Icon > Applications > Version & Licenses.
    1. Update/Install the Jira Service Management application to the latest version.
  12. Re-install plugins via file the Cog Icon > Add-ons > Find new add-ons.
    1. If preferred, upload the add-ons manually via Cog Icon > Add-ons > Manage add-ons > Upload add-on.
      (warning) Not all plugins are compatible with Jira 7.13.latest. Ensure to verify compatibility first!
  13. Test and ensure that the instance is functioning to satisfaction.
  14. Jira を再起動します。
  15. Perform a 

Known Problems

Login to https://jira.atlassian.com to enable the display of issue details below.


問題回避策

JRASERVER-69138 - 課題詳細を取得中... ステータス

Available in the bug ticket. Fixed in Jira 7.13.4

JSWSERVER-15748 - Getting issue details... STATUS

Delete the old entries in entity_property table prior to triggering upgrade.

JRASERVER-64928 - 課題詳細を取得中... ステータス

Add additional table index to entity_property table. Fixed in 8.0.
JRASERVER-65168 - 課題詳細を取得中... ステータス
Add additional table index to propertyentry table. Fixed in 8.0.

JRASERVER-63002 - 課題詳細を取得中... ステータス

Add additional table index to changeitem and changegroup tables. Fixed in 8.0

JRASERVER-69822 - 課題詳細を取得中... ステータス

Jira can index stale custom field values in Data center. Affecting 7.13.4 and 7.13.5. Fixed in 7.13.6+

最終更新日 2021 年 9 月 14 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.