JIRA Service Desk 3.8.x upgrade notes

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

You should also 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. You can start JIRA from the command line with your add-ons disabled if you're having issues.

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

Information for JIRA developers

You should check these resources for additional info:


Events for creating and deleting issue links

We've introduced new events for creating and deleting issue links, which might be handy while developing your plugins. The new events are IssueLinkCreatedEvent  and  IssueLinkDeletedEvent, and if you want to use them for webhooks, you should use:

  • create (issuelink_created)
  • deleted (issuelink_deleted)

Information for administrators

New JDBC driver for Microsoft SQL Server

We've shipped a new driver for Microsoft SQL Server, which requires that you update the driver's URL in the dbconfig.xml file. In most cases, it's enough to run the JIRA configuration tool, which will update the URL automatically, but if you've customized the URL by adding some properties to it, you might need to make the changes manually. For more details on how to do this, see Updating JDBC URL.

When you start JIRA after the upgrade, you'll get an error message until you fix this issue.

 

JIRA will fix corrupted indexes by itself

We've made this change already in 7.4.2, but we just wanted to make sure you know about it. JIRA now has an automatic recovery of corrupted indexes, which saves you a lot of manual work, but there's a catch. The broken documents will be deleted from the indexes, and this might result in e.g. JQL not being able to find some issues. You can recognize that your indexes were being fixed by searching the atlassian-jira.log file for a line like this one:

2017-07-18 23:51:49,990 JIRA-Bootstrap ERROR      [c.a.jira.index.LuceneCorruptionChecker] Index '/jirahome/caches/indexes/issues' is broken: 2 bad segments.
    Performing healing the index. 2 documents will be lost

All deleted documents can be recreated by running a reindex in JIRA. For more details, see Lucene index corruption

 

Version specific detail

  • Check the JIRA application compatibility matrix to ensure you have the most up to date, compatible versions.

    • Upgrading from a 3.1 or later version - There are no known issues. 
    • Upgrading from a 3.0 - There is a known issue regarding gadgets, and there is a workaround described in the JIRA Service Desk 3.1.x upgrade notes.
    • Upgrading from a version earlier than 3.0 - Please consult the Migration hub as it contains information on important user management, application access and log in changes. You must upgrade to JIRA Service Desk 3.0 before upgrading to JIRA Service Desk 3.8.
Last modified on Sep 5, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.