JIRA Service Desk 3.1.x upgrade notes

Please follow the instructions in the general Upgrading Jira applications guide, as well as the JIRA Service Desk 3.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.

This page also describes known issues as well as changes you should be aware of before deciding whether or not to upgrade to JIRA Service Desk 3.1.x.

On this page:

Information for JIRA developers

See Preparing for 7.1 for JIRA platform important information that could affect your add-ons or scripts. Also, see our Java API policy for JIRA.

JIRA gadget rendering change

In JIRA platform 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.