JIRA Service Desk 3.9 Long Term Support release change log

• Group customers into organizations.
• Customize email notifications.
• Agents can add portal announcements.
• Rich text editing.
• Project administrators can edit their project workflow.
• Changes to starting a JIRA instance.
• Data Centre single sign-on.

• Updated project templates.

• Non-customer comments enabled.
• Creating customers from email address lists.

• Improved SLA rendering.
• Extended project administration.
• JIRA Service Desk Data Centre zero downtime upgrades.
• Improvements to issue export.
• In-app notifications.

• Canned responses.

• Importing SLAs from existing projects.
• Events for linked issues.
• Syntax highlighting for new languages.

• Better canned responses.
• Auto approvals.
• Live monitoring with JMX.

• Better security with X-Frame-Options.

• More languages supported.

• Priority schemes from 3.9.4 only.

• Using http://jira/jira breaks Queues and Reports in Service Desk view
• TimedPromiseExecutionRegistry causes OOM
• JIRA filter for a queue that has an uncaught exception breaks Queues view
• SD redirects calls to any plugin's REST endpoints to /servicedesk/customer/portal/1

• All Service Desk related pages are not loading in IE 11

No critical bug fixes.

No critical bug fixes.

No critical bug fixes.

• Notifications are not sent to Reporters and Request Participants until an application restart

Ended support for:

• Microsoft SQL Server 2008
• Postgres 9.0 and 9.1
• MySQL 5.1
• Internet Explorer 10

Ended support for:

• Postgres 9.2

• If you're upgrading to JIRA Service Desk 3.3 and MySQL 5.7.6 or above, you need to make sure your JIRA user has the REFERENCES permission.
• If you're running your JIRA application over SSL, and have configured Apache Tomcat with HTTPS, you'll need to update your server.xml HTTPS connector with the correct protocol or JIRA will fail to start.

No known issues.

Performance issues:

• Versions 3.5.1 and 3.5.2 have performance issues and show errors while opening pages or finishing some actions. This applies only if you’re using postgreSQL and have more than 500k users.

Important notes:

• If you're planning to use MySQL 5.7.6 or later, you'll need to grant your database user an extra permission (REFERENCE).
• If you're running JIRA over SSL, you'll need to update your server.xml with the correct protocol because of the Apache Tomcat upgrade.
• We've disabled automatic XML backups. Use your native database tools to create a backup.

Important notes:

• New options added to the startup files to enable garbage collection. Just a heads up, no actions required.

Important notes:

• New JDBC driver for Microsoft SQL Server requires a new URL. If you didn't modify the original URL, you can fix it with JIRA configuration tool. If you customized the URL, you might need to change it manually.

Important notes:

• Changes to priority schemes (project-specific priorities feature) will not affect your current configuration.

Known issues:

• A fix for duplicated job IDs requires extra steps in some instances, just to be sure (checking the database if the index was created; restarting your JIRA instance.)