JIRA Service Desk 3.5.x release notes

Release notes for earlier versions of Jira Service Management

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

This JIRA Service Desk release has reached its end of life. See End of life policy.

The JIRA Service Desk team is pleased to announce the release of JIRA Service Desk 3.5!

In this release of JIRA Service Desk, we've worked on simplifying email interactions by allowing non-customers to comment on existing requests via email (previously this would have created a new request), and allowing the JIRA admin to decide if new customers can be created from the To and CC fields of incoming emails.

We hope these changes in JIRA Service Desk 3.5 help deliver a better experience for both our customers and their customers.

If you've got any comments or suggestions, please feel free to send them directly to us in our JIRA instance.

Vidhu Sharma

JIRA Service Desk product manager

Download the latest version
Or upgrade your existing JIRA Service Desk application.

On this page:

Non-customer comments

In previous versions of JIRA Service Desk, when a person who was not already a customer or participant on a request replied to an email related to an existing request within that service desk, that reply would create a new request. This could be confusing for both the customer and the agents involved in the request.

We've now added an option on the Email requests page which allows the service desk admin to decide if they want to allow non-participants and external people to comment on existing requests via email. When enabled, and if your service desk allows public sign-up, we'll add the comment and create a customer account for the email sender. If public sign-up is disabled, we'll disregard the email.

Creating customers from email address lists 

We've added another option on the Email requests page that allows you to choose how JIRA Service Desk creates customers from the To and CC fields of emails. 

This features works together with the non-customer comments feature to give you more control and flexibility on who can do what in your JIRA Service Desk instance. To navigate to the setting, select  > Applications > JIRA Service Desk > Email requests.

Resolved issues

Performance issues

We’ve noticed that 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. To work around it, increase the heap size by 1GB per million users. We’ll release a fix for this in the next bugfix release.

Issues resolved in 3.5.0

In this release, we've made some minor improvements to JIRA Service Desk, which includes some important fixes to how our automation works, which will improve speed and performance. For more details on that particular fix, see  JSDSERVER-4896 - Getting issue details... STATUS .

Key Summary T P Status Resolution

Issues resolved in 3.5.1

Released on 5 June 2017 

Key Summary T P Status Resolution

Issues resolved in 3.5.2

Released on 19 June 2017


In this release, we've included the Atlassian Notifications add-on, which provides targeted notifications, primarily to JIRA administrators, regarding new releases and upcoming maintenance renewals.

If you're a JIRA administrator and don't want to receive such notifications, you can go to  > Add-ons > Manage add-ons, search for Atlassian Notifications among the system add-ons, and disable it. For more info, see Disabling and enabling add-ons.


Key Summary T P Status Resolution

Issues resolved in 3.5.3

Released on 11 January 2018

Key Summary T P Status Resolution

Last modified on May 7, 2019

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.