JIRA Software 7.1.x upgrade notes
This JIRA release has reached its end of life. See End of life policy.
Before you begin
Sometimes we find out about a problem with the latest version of JIRA Software after we have released the software. In these cases, we publish information about the known issues in the Jira Knowledge Base. Please check for known issues and follow the instructions as necessary.
What do I do if I have problems with JIRA Software?
If you have problems when installing/upgrading JIRA Software or using it after an upgrade, please contact our support team. This 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 Software, they will escalate it to our development team.
Please follow the instructions in the general Upgrading Jira applications guide, as well as the JIRA Software 7.1.x specific instructions below. The general guide contains important tasks that are essential for getting your upgraded JIRA installation to work correctly and, if necessary, migrating existing configurations.
Also, please make sure that your licenses and add-ons are all up-to-date. Removing any incompatible add-ons before upgrading may help you avoid problems during your upgrade process. You can check the compatibility of your add-ons before your upgrade using the JIRA update check.
This page also describes known issues as well as changes you should be aware of before deciding whether or not to upgrade to JIRA Software 7.1.x.
On this page:
Upgrading to JIRA Software 7.1
If you're using JIRA and JIRA Agile, and you want to upgrade to the latest version of JIRA Software, we recommend you upgrade to the latest version of JIRA Software 7.0.x first. We recommend the following upgrade path:
JIRA + JIRA AGILE → JIRA SOFTWARE 7.0 → JIRA SOFTWARE 7.1 (latest version)
The recommended, intermediary upgrade version is necessary due to upgrade tasks that were removed in JIRA Software 7.1.0.
As an alternative, you can upgrade to an intermediary version of JIRA Agile (any version above, and including, 6.4.5), which includes the upgrade tasks that were removed.
See the Migration Hub for more information on upgrading to JIRA Software 7.0.
To upgrade from JIRA Software 7.0 to JIRA Software 7.1, please see Upgrading Jira applications.
Please read JIRA Software 7.0.x release notes and JIRA Software 7.1.x release notes.
In addition to this upgrade path, please read the Upgrade Notes for every version of JIRA Agile you are skipping.
Information for JIRA developers
See Preparing for 7.1 for important information that could affect your add-ons or scripts. Also, see our Java API policy for JIRA.
JIRA gadget rendering change
In JIRA 7.1 there was a change in gadgets, and now a number of charts are generated using Javascript in the browser rather than server-side. This has significant performance improvements as the server is offloading processing to the browsers and results in less CPU usage. As a side effect of this, we've now exposed a previous configuration problem where the symptom now is the gadget tags do not properly render because they're not able to retrieve the translation strings for JIRA. Gadgets title are showing as __MSG_gadget.xxxxxxx, __MSG_gadget.activity., __MSG_gadget.filter, _MSG_gadget.project.title_ and so on. This only affects a small percentage of instances, and can be fixed by making sure that JIRA can communicate with itself correctly. Please see the related KB for more details and fixes if you're experiencing this problem after upgrading: How to fix gadget titles showing as __MSG_gadget.