Upgrade to version 7.2x of Jira

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

目的

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

準備

はじめる前に

  • Check Jira 7.2 Supported Database Versions:
    • Oracle 12c
    • MySQL 5.5, 5.6
    • PostgreSQL 9.2, 9.3, 9.4
    • Microsoft SQL Server 2012, 2014
  • 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 plugins 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 version matrix. Jira 7.2 uses AppLinks 5.2.3, based on that, minimal versions for Jira 7.2 for other applications:
    • Bamboo 5.10+
    • Confluence 5.6+
    • Crucible/Fisheye 3.6+

    • Stash 3.4+
  • Review the Recommended Readings (links to the right)

Optimizing the Upgrade Process

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

  • Disable Upgrade Index and Automated Upgrade Backup

  • (For Jira <= 7.2.7) Apply the workaround for JRA-61383. In large installations the upgrade rename of "Agile" fields to "Software" increases the length of your outage. Doing this via SQL is fast and low risk so long as you test your upgrade procedure in advance.

テスト

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: Establishing staging server environments for JIRA applications.

On this page




Upgrade Steps for Jira Software

Before Proceeding

  • Using Jira Agile ? - Ensure to first upgrade the Jira Agile add-on to the latest version compatible with your version of Jira. Jira Agile version must be 6.4.5 or greater before proceeding.
  • Using Jira Service Management? - Ensure to first upgrade to Jira to version 7.0 and Jira Service Management to version 3.0 (or later in the 7.0.X and corresponding 3.0.X range)

  • Third-party plugins may have upgrade requirements, please ensure to be familiar with these requirements as it may require additional intermediate upgrade steps

Supported Database Versions:

  • Oracle 12c
  • MySQL 5.5, 5.6
  • PostgreSQL 9.2, 9.3, 9.4
  • Microsoft SQL Server 2012, 2014

Upgrading to Jira Software 7.0.latest

Required if upgrading from Jira 6 with Service Management. Skip to next section if not using Service Management.
  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. Please check that all Jira bundled plugins are enabled (eg: jira-importers-plugin). Check pluginstate table. 
  5. 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 DataCenter, also remove (and backup) <Shared>/plugins/ folder 
  6. Modify the dbconfig.xml file in the newly copied Jira_HOME
    1. Configure the file to point to the newly copied database
  7. Download the latest Jira Software 7.0.x Archive version
  8. Extract the Jira Software 7.0.latest archive to a new target Jira_INSTALL folder
  9. Configure your Jira Home folder path and point to the newly copied Jira_HOME
  10. Create a jira-config.properties file in your Jira Home folder (Edit the jira-config.properties file in Jira server) and add the options below:

    upgrade.reindex.allowed=false
    jira.autoexport=false
    1. If the file already exists, simply add these lines to the start of the file
    2. These parameters will disable the automated upgrade backup and automated index after upgrade
  11. 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
  12. Start Jira and review the logs to ensure the upgrade completed successfully.
  13. Navigate to Cog Icon > Applications > Version & Licenses.
  14. Click on Install in the Jira Service Management application. This should install version 3.0.11
  15. Re-install plugins via the Cog Icon > Add-ons > Find new add-ons
    1. If prefered, upload the add-ons manually via Cog Icon > Add-ons > Manage add-ons > Upload add-on

      Not all plugins are compatible with Jira 7.2.latest. Ensure to verify compatibility first!
  16. Test and ensure that the instance is functioning to satisfaction
    1. Perform a 
  17. Proceed to next section for upgrading to 7.2.latest

Upgrading to Jira Software 7.2.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 DataCenter, also remove (and backup) <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.2.latest Archive version
  7. Extract your Jira Software 7.2.latest to a new target Jira_INSTALL folder
  8. Configure your Jira Home folder path and point to the newly copied Jira_HOME
  9. Create a jira-config.properties file in your Jira Home folder (Edit the jira-config.properties file in Jira server) and add the options below:

    upgrade.reindex.allowed=false
    jira.autoexport=false
    1. If the file already exists, simply add these lines to the start of the file
    2. These parameters will disable the automated upgrade backup and automated index after upgrade
  10. 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
  11. Start Jira and review the logs to ensure the upgrade completes successfully
  12. If using Service Management, navigate to Cog Icon > Applications > Version & Licenses
    1. Update/Install the Jira Service Management application to the latest version
  13. Re-install plugins via file the Cog Icon > Add-ons > Find new add-ons
    1. If prefered, upload the add-ons manually via Cog Icon > Add-ons > Manage add-ons > Upload add-on

      Not all plugins are compatible with Jira 7.2.latest. Ensure to verify compatibility first!
  14. Test and ensure that the instance is functioning to satisfaction
  15. Jira を再起動します。
  16. Perform a 


Bugs Fixed in Jira Software 7.2

JSWSERVER-14707

Javascript errors when dragging issues on Kanban board


JSWSERVER-14563

Project Import fails due to SprintAO does not have field GOAL


JSWSERVER-14288

DVCS Connector not syncing - "WaitForAO" java.lang.NullPointerException


JSWSERVER-13980

[設定] をクリックする際、プロジェクト レポートが複数選択に失敗するで


JSWSERVER-13756

Third-party apps that create multiple subtasks as part of workflow operations may trigger LexoRank deadlocks


JSWSERVER-13744

Tempo Timesheets 8.0 を使用するとアジャイルボードがレンダリングされない


JSWSERVER-13206

Lexorank making quick create issue not quick


JSWSERVER-13163

LexoRank database query performance is slow due to the way the field is constructed


JSWSERVER-12984

アクティブなスプリントから課題を削除するときにエラーが発生する


JSWSERVER-12898

Quick filter is not remembered after navigating to another board


JSWSERVER-12348

Jira Agile のカンバンボードに Firefox の「応答のないスクリプト」警告が表示される


JSWSERVER-12221

JIRA Agile performs slowly when using Microsoft SQL Server


JRASERVER-68143

Jira Data Center Installation guide incomplete about copying cache folder to shared home


JRASERVER-67537

Updating jira documentation about (no downtime) phrase


JRASERVER-67490

Request for documentation review: Connecting to an LDAP directory


JRASERVER-67310

Documentation incorrectly says that NFS for shared storage isn't supported


JRASERVER-66976

Managing users documentation is ambiguous in regards to the term 'administrator'


JRASERVER-66873

Misleading / Incorrect Global permission for Outgoing mail configuration indicated in the documentation


JRASERVER-66684

JIRA Installation Documentation - Connect Database Review


JRASERVER-66661

Update Reserved Words section for JQL Searching KB


JRASERVER-66069

Captcha appears warped and unreadable and chart gadgets that print graphics show garbled text and weird symbols when running JIRA in Linux


JRASERVER-65783

Update additional UTF parameter in the JIRA startup documentation


JRASERVER-65162

Misleading JIRA Core Documentation on Versions


JRASERVER-64364

Configuring JIRA application options doc incorrect defaults


JRASERVER-64063

Header menu do not work on view issue page on Firefox 50.1 or above


JRASERVER-63594

Pipe (|) in the beginning of an e-mail's body makes it so that the comment is not inserted properly on a issue


JRASERVER-62742

ユーザーの同期中、非アクティブユーザーごとにアクティブユーザー数が再計算される


JRASERVER-62613

Duplicate fields when creating Issue from Project Does Not Exist page


JRASERVER-62497

Update to a version of the HipChat plugin that contains a fix for HC-32766


JRASERVER-62496

CVE-2016-6668 - リンクされている Hipchat インスタンスとの通信に使用する秘密鍵が、様々な製品用 Hipchat プラグインから漏れている


JRASERVER-62434

Concurrency problems with project and issue related REST APIs


JRASERVER-62390

Update/certify JIRA Charting Plugin for compatibility with JIRA 7.2


JRASERVER-62389

Update/certify JIRA Calendar Plugin for compatibility with JIRA 7.2


JRASERVER-62201

委任 LDAP を使用している場合、Secure SSL フラグが機能しない


JRASERVER-62062

Upgrade bundled Java to 8u101+


JRASERVER-62040

When opening issues, that contain sub-tasks, the view is automatically positioning at the sub-task area


JRASERVER-62035

ブラウザーコンソールに「Uncaught TypeError: Cannot read property 'left' of null」というエラーが表示され、ダッシュボードの読み込みが失敗する


JRASERVER-62006

Jira 7.2 RC02 が MySQL のエラーをスローする


JRASERVER-61977

Sub-Task items broken in JIRA Local Help


JRASERVER-61879

Columns order changed by JIRA randomly for newly saved filter


JRASERVER-61862

XSS in the jira-mobile plugin.


JRASERVER-61851

Components drop down menu on jira.atlassian.com broken


JRASERVER-61625

Cannot use the keyboard to navigate header dropdowns


JRASERVER-61471

Activity Stream: Translation error (german)


JRASERVER-61465

PDF images do not display correctly in high resolution / retina display clients


JRASERVER-61444

JQL suggestions popup is not closed sometimes when typing fast


JRASERVER-61442

When viewing a dashboard as a wallboard, the gadget table header background is white


JRASERVER-61371

IE 11 , attached PDF view in issue is broken


JRASERVER-61356

the hotkey g + i for "find issue" does not navigate to Issue navigator


JRASERVER-61320

Hiding Components field in field configuration breaks Components page in project admin

JRASERVER-61243

Correct misspelled getPrefences() to getPreferences() in file createdvsresolved-gadget.xml


JRASERVER-61198

JIRA Background Reindexing fail due NullPointerException in fixupConcurrentlyIndexedIssues stage


JRASERVER-61052

Editing an issue collector causes browser to crash


JRASERVER-60747

JIRA with delegated LDAP directory connected through crowd does not auto synchronize user details and groups on first login


JRASERVER-60561

課題セキュリティスキームを削除しても課題から削除されず、アクセスできない状態でレンダリングされる


JRASERVER-60532

Slow query in user picker : DefaultUserPickerSearchService


JRASERVER-60530

Gadgets server-to-server connectivity errors are swallowed, we should log them instead


JRASERVER-60365

Can not build JIRA 7.1 from source


JRASERVER-60236

In-product link to "Managing user access to JIRA applications" results in 404 Page Not Found


JRASERVER-60224

課題コレクター管理ページを表示するとすべての課題がメモリに読み込まれる


JRASERVER-60204

PDF preview not working properly on IE11


JRASERVER-60108

Keyboard shortcuts triggering while typing into a user selector


JRASERVER-60058

Can't change assignee field in View Issue screen But can change in view screen with AllOpenIssue Filter.


JRASERVER-60039

HTML on workflow validation's failure messages not being rendered


JRASERVER-60032

7.1 bundled plugin versions missing from marketplace with newer plugin versions not compatible with 7.1


JRASERVER-60027

Column scrolling doesn't work in Issue Navigator


JRASERVER-59989

Broken Link to Documentation on Database Setup page.


JRASERVER-59781

Permission Scheme cannot be edited when it includes a single user


JRASERVER-59076

Inconsistent behaviour when anonymous user trying to reach existing and non existing issue


JRASERVER-46052

i18n English message is buggy - apostrophe should be doubled


JRASERVER-45967

Default Avatar is not displayed on Email Notifications


JRASERVER-45794

Atlassian-jira.log shows 'Dangerous use of multiple connection' warnings due to a process holding a database connection for longer than 5 minutes


JRASERVER-45746

Documentation for JIRA Data Center upgrade


JRASERVER-45512

Copy & paste multi line text to description or comment scrambles line breaks


JRASERVER-45329

List of users may be misplaced outside of browser window when using @mentions


JRASERVER-45161

Deleting an Issue Type can result in a NullPointerException when attempting to perform a number of actions within JIRA


JRASERVER-45032

Import progress page can sometimes return code 500 status if refreshed


JRASERVER-42654

Email notification shows broken image when there is no default image set in gravatar


JRASERVER-42409

A JIRA issue description is silently discarded if it contains a specific unicode character


JRASERVER-40084

Large Image Files (> 100MB) in avatar picker causing OOME


JRASERVER-39173

Specify logging level to Prevent Root DEBUG from Exposing Login


JRASERVER-35084

XSS in admin/ViewIssueFields.jspa


JRASERVER-32688

An attachment with an issue key in its file name cannot be rendered as an inline image in an issue


JRASERVER-21443

3 つより多い「並び順」基準を使用すると、フィルターの結果ガジェットのソートが機能しない


Suggestions Implemented in Jira Software 7.2

JSWSERVER-19903

Ability to clone an issue without cloning Agile sprint information


JSWSERVER-16558

Typo In Installing Jira On Linux Documentation Referencing Windows service


JSWSERVER-15172

Request for documentation to be updated regarding Issue Status section in project summary page


JSWSERVER-11304

アジャイルボード上のエピックリンクをエピックにリンクすべき


JSWSERVER-9719

プロジェクト別のスイムライン


JSWSERVER-8938

ラピッドボードユーザーの場合、課題が属しているスプリントを詳細ビューに表示できるようになると便利


JSWSERVER-8465

As a user, I would like the Component field to show links for the values displayed in the Detail View (to be consistent with JIRA)


JSWSERVER-7893

Inline-Editable Fields in the Issue Detail View


JSWSERVER-6541

Ability to clone an issue without cloning Agile sprint information


JSWSERVER-6134

Allow to edit/delete "Comments" in the Issue details panel


JSWSERVER-6015

Ability to link to comment in JIRA View Issue from Agile detail view


JSWSERVER-5870

Allow to delete attachments


JSWSERVER-5865

Add ability to remove issue links on Detail view, not just add them


JSWSERVER-5664

Ability to sort attachments in Agile detail view


JSWSERVER-5570

Make fix version a link in the Agile board detail view


JSWSERVER-4515

Add issue type as configurable field for Issue Detail View


JRASERVER-66875

Improve visibility of known issues of Jira and MySQL in documentation


JRASERVER-66730

Incorrect path in documentation


JRASERVER-66629

Update JIRA Supported Platforms page to prefer Java CPU releases rather than PSU


JRASERVER-65537

ドキュメントに Jira のバージョンを選択するオプションがない


JRASERVER-65126

ユーザー用の Lucene メモリ内インデックスを実装


JRASERVER-64040

Documentation Enhancement - "Update User attributes on Login" for Delegated LDAP Directories


JRASERVER-63690

Jira インストールガイドの改善


JRASERVER-61008

Deleting a link removes reciprocal without regard


JRASERVER-34423

Add the ability to update issues via REST without sending notifications


JRASERVER-32948

内部および外部グループに関して [入れ子グループの管理] ページを更新


JRASERVER-8943

WYSIWYG / リッチテキストエディター


JRASERVER-8580

課題ナビゲーターから CSV をエクスポート

Known Problems

問題回避策
This is a one-time occurrence until Jira is restarted.
Upgrade to Jira 7.0.latest + Service Management 3.0.11 before then upgrading to Jira 7.2.latest.

Access the index admin page and use the Copy the Search Index from another node functionality.

Fixed as of Jira Core 8.19.1, 8.20.0

The workaround is to modify the export URL and set a value. Please refer to the bug report for full details.

Fixed as of Jira Core 7.4.0, 7.2.11, 7.3.9

Currently, Structure Plugin has been identified to be able to prevent Jira Data Center from locking the index. The structure has fixed this as of v3.3.3, please upgrade.

Workaround is to update the changes in the Jira database before upgrading. Please refer to the bug report for full details.
Fixed as of Jira Software 7.2.8

The problem is due to querying for unarchived versions. Ensure to archive any versions that are not actively used by the system to help improve speeds.
Managed Sprints PermissionUsers may experience Sprint permissions issues as Jira introduced the "Manage Sprints" permission. This may result in users noticing the inability to perform Sprint actions. If problems arise, please check the permissions for users:

Re-index Jira.
Fixed as of Jira Software 7.2.7

Using database native backup tools when creating backups. If it is required that Jira can generate backup XMLs, use the Oracle 11g driver.
Fixed as of Jira Core 7.2.7

Update bundled Oracle driver from 12.1.0.1 to 12.2.0.1 version

See workaround section in the ticket.

Fixed as of Jira Core 7.2.13, 7.6.4, 7.7.2, 7.8.0

See workaround section in the ticket. 

Fixed as of Jira Core 8.0

説明 To help provide a detailed guide to help with the upgrade process of large scale and business critical Jira environments to Jira 7.2.latest. Other methods for upgrade also exist, see here: Upgrading JIRA applications
製品Jira
プラットフォーム

Server

Data-Center



最終更新日: 2025 年 1 月 29 日

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

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