JIRA Agile 6.3 Upgrade Notes

 

Upgrading to JIRA Agile 6.3 is free for all customers with an active GreenHopper license.

If you are using GreenHopper "behind-the-firewall" (that is, if GreenHopper is installed on-premises at your site), you can upgrade via the JIRA Plugin Manager. Before upgrading, please read the notes on this page.

If you are using JIRA Agile OnDemand, please watch the JIRA Agile OnDemand Release Summary for the latest updates.


Upgrading from GreenHopper 6.2.x, 6.1.x, 6.0.x, 5.10.x, 5.9.x, or 5.8.x to JIRA Agile 6.3

Please follow the upgrade instructions in the JIRA Agile Installation and Upgrade Guide, plus note the following:

Go to GreenHopper in the UPM

To upgrade to JIRA Agile 6.3, please navigate to Atlassian GreenHopper in the Universal Plugin Manager, i.e. JIRA Administration > Add-Ons > Atlassian GreenHopper.

Note, you will see an upgrade message saying 'A free update (v. 6.3.x.x) is available for this add-on.' Click Update. This will upgrade your GreenHopper add-on and rename it to JIRA Agile.

From JIRA Agile 6.3.0 and later, you will see 'JIRA Agile' not 'Atlassian GreenHopper' in the Universal Plugin Manager.  

Compatible with JIRA 5.1.x and higher

JIRA Agile 6.3 is only compatible with JIRA 5.1.x and higher.

Issues now belong exclusively to sprints

Please read Sprint Marker Migration for important information about how this will affect your data.

Schedule Issues permission required for adding/removing an issue from a sprint

The act of adding/removing an issue for a sprint also involves ranking the issue, as you can drag and drop the issue to any point in the sprint. Hence, these two actions now require the Schedule Issues permission, in addition to the Edit Issues permission. Read more...

Re-index if subtasks or swimlanes don't display/work correctly

If subtasks or swimlanes are not displaying/working correctly after the upgrade, you may need to reindex JIRA.

Re-index recommended if using Epics

A JIRA re-index is recommended before you start using epics.

Re-index required if upgrading from 5.9.7 or older

A JIRA re-index is required for anyone upgrading from a GreenHopper version older than 5.9.7.

If upgrading from 5.8.3, manual upgrade is required

If you are upgrading from GreenHopper 5.8.3, please:

  1. Download JIRA Agile manually from the Atlassian Marketplace.
  2. Install it using the instructions for Installing by file upload — see Installing Marketplace apps.

Other known issues

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.

If you encounter a problem during the upgrade and cannot solve it, please create a support ticket and one of our support engineers will help you.

Upgrading from GreenHopper 5.7.x or earlier

In addition to the above, please read the GreenHopper 5.8 Upgrade Notes and the Upgrade Notes for every version you are skipping during the upgrade. The complete list of Upgrade Guides is available here.

Re-index and restart required

Please re-index and restart JIRA after ugrading to JIRA Agile 6.3 from GreenHopper 5.7.x or earlier.

For the developers

Please note, the "sprints" REST resource has been renamed to "sprintquery".

Last modified on Sep 5, 2013

Was this helpful?

Yes
No
Provide feedback about this article

In this section

Powered by Confluence and Scroll Viewport.