JIRA Agile 6.4 Upgrade Notes

JIRA Agile 6.4 Release Notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

This page contains important JIRA Agile 6.4-specific tasks that are essential for getting your upgraded installation to work correctly. Follow the instructions in the general JIRA Agile Installation and Upgrade Guide together with the instructions below.

If you are using JIRA Agile in OnDemand, subscribe to the Atlassian OnDemand blog (see this page for instructions) to find out when your site will be updated with this release. Please note, JIRA Agile OnDemand may be updated several days after the release of downloadable JIRA Agile (that is, JIRA Agile for installation on-premises at your site).

On this page:

Before you begin

Before you begin the upgrade, please check for known issues. Sometimes we find out about a problem with the latest version of JIRA Agile after we have released the software. In such cases we publish information about the known issues in the JIRA Agile Knowledge Base. Please check for known issues and follow the instructions as necessary.

What do I do if I have problems with JIRA Agile?

If you have problems when installing/upgrading JIRA Agile or using it after an upgrade, please contact our support teamThis is the fastest way to get your problems addressed. The support team can work with you to figure out what is going wrong, and if there is a bug with JIRA Agile, they will escalate it to our development team. 

Upgrading from JIRA Agile 6.3 to JIRA Agile 6.4

(Important) Changes to the Rank field

We have made a number of changes to the Rank field in JIRA Agile to support upcoming JIRA features. You shouldn't notice any difference in how the Rank field works, but there are upgrade tasks that you should be aware of:

Upon upgrading to JIRA Agile 6.4:

  • sprint marker migration will be automatically triggered for all boards that have not been migrated yet. If you use Scrum and future sprints, make sure that you read Sprint Marker Migration before you upgrade.
    In particular, note that the order in which your boards are migrated can affect the association between issues and sprints. This is important because you won't be able to choose the order that your boards are migrated when upgrading to JIRA Agile 6.4 — boards will be automatically migrated in this order:
    Boards that are most frequently visited will be migrated first. If two or more boards have an equal number of visits, then the most recently created board will be migrated first.
    If you want control over the order of migration for your boards, manually migrate your boards before you upgrade to JIRA Agile 6.4.
  • The current (pre-6.4) Rank custom field will be renamed to Rank (Obsolete). The Rank (Obsolete) field is redundant and can be deleted, if you choose. The old Rank field will be replaced by a new field, also named Rank.
    • Saved filters that rely on the old Rank field will be automatically changed to use the new Rank field.
    • If you use the Rank (Obsolete) field in a filter for a board, then ranking will be disabled for the board.
    • The new Rank field uses alphanumeric values (e.g. '0|1004g') rather than numeric values like the old Rank field. The new values won't make sense when viewing them, but you can still use the Rank field to sort issues.
  • If you are using downloadable JIRA (not OnDemand), a background reindex will be triggered. Each board will be inaccessible until 90% of the issues on it have been reindexed. We recommend that you lock JIRA and rebuild the index, if you can plan time for it.

Compatible with JIRA 6.0.x and higher

JIRA Agile 6.4 is only compatible with JIRA 6.0.x and higher. See Supported Platforms for details.

Upgrading from GreenHopper 6.2.x or earlier to JIRA Agile 6.4

In addition to the points listed above, please read the Upgrade Notes for every version of JIRA Agile you are skipping. In particular, ensure that you read the GreenHopper 5.8 Upgrade Notes if you are upgrading from 5.7 or earlier. 

(Important) Staging your upgrade for the sprint marker migration

Ensure that you read the '(Important) Changes to the Rank field' section above. As noted in that section, upgrading to JIRA Agile 6.4 will trigger an automatic sprint marker migration for all boards.

If you use Scrum and future sprints, you may want to control the order of migration for your boards. In this case, we recommend that you upgrade to JIRA Agile 6.3 first, manually migrate your boards, then upgrade from JIRA Agile 6.3 to JIRA Agile 6.4.

Other notes

  • GreenHopper was renamed to JIRA Agile in JIRA Agile 6.3. From JIRA Agile 6.3.0 and later, you will see 'JIRA Agile' not 'Atlassian GreenHopper' in the Universal Plugin Manager.   
  • Re-index and restart JIRA, if you are upgrading from 5.9.7 or older
  • If upgrading from 5.8.3, you must upgrade manually — download the JIRA Agile add-on separately (from theAtlassian Marketplace) and install the add-on file by upload, as described here: Installing add-ons.
Last modified on Jun 2, 2014

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.