JIRA Service Desk 3.9.x upgrade notes

Release notes for earlier versions of Jira Service Management

On this page

In this section

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

This JIRA Service Desk release will reach its end of life on November 16, 2019. See End of life policy.

Here are some important notes on upgrading to JIRA Service Desk 3.9. For details of the new features and improvements in this release, see the JIRA Service Desk 3.9.x release notes. As JIRA Service Desk runs on the JIRA platform, you should also view the JIRA platform 7.6 upgrade notes.

JIRA Service Desk 3.9 is a Long Term Support release
This means we'll provide bug fix releases until 3.9 reaches end of life, to address critical security, stability, data integrity, and performance issues. 
Ready to upgrade? Check out the JIRA Service Desk 3.9 Long Term Support release change log for a roll-up of changes since 3.3. 

Upgrade notes

Priority schemes (UI changes) - JIRA Software, JIRA Core and JIRA Service Desk 3.9.4 only

We've made significant changes to how priorities are managed in JIRA, but these changes are only available from JIRA Service Desk 3.9.4. Currently, your JIRA Service Desk projects are using a global list of priorities. After the upgrade, all these priorities will be moved to the default priority scheme, which works in the same way. You can create new schemes and make use of them in JIRA Core or JIRA Software, but you will only be able to use them with JIRA Service Desk projects from 3.9.4.


Priority schemes (API changes)

We encourage everybody to get familiar with these changes, but they're more important for plugin developers rather than JIRA admins. The APIs that would allow JIRA admins to manage priority schemes outside of the user interface will not be available in JIRA 7.6.

If you're a plugin developer and want your plugin to manage priority schemes, take a look at this list of API changes. We've not only added new APIs that allow plugins to manage priority schemes, but we also changed the existing ones, which will most likely make your plugins incompatible. This is for priority schemes, the APIs for managing priorities don't change, but bear in mind that the current global list of priorities now becomes the default priority scheme, so your plugins might retrieve inaccurate data regarding priorities themselves.

What's new?

We're adding these APIs to allow plugins to manage priority schemes. 

Show me the changes...
ClassnameMethod signatureJavadoc
com.atlassian.jira.issue.fields.config.manager.PrioritySchemeManager

FieldConfigScheme createWithDefaultMapping(String name, String description, List<String> optionIds);

Doc

FieldConfigScheme updateWithDefaultMapping(FieldConfigScheme fieldConfigScheme, List<String> optionIds);

Doc

FieldConfig getFieldConfigForDefaultMapping(FieldConfigScheme fieldConfigScheme);

Doc

 void delete(FieldConfigScheme fieldConfigScheme); Doc

FieldConfigScheme getScheme(Project project);

Doc

FieldConfigScheme getScheme(Long id);

Doc

 List<FieldConfigScheme> getAllSchemes(); Doc

 boolean isDefaultScheme(FieldConfigScheme fieldConfigScheme); Doc

 FieldConfigScheme getDefaultScheme(); Doc

 String getDefaultOption(IssueContext issueContext); Doc

 String getDefaultOption(FieldConfig fieldConfig); Doc

 void setDefaultOption(FieldConfig fieldConfig, String optionId); Doc

 List<String> getOptions(IssueContext issueContext); Doc

 List<String> getOptions(FieldConfig fieldConfig); Doc

 void setOptions(FieldConfig fieldConfig, List<String> optionIds); Doc

 void addOptionToDefault(String optionId); Doc

 void removeOptionFromAllSchemes(String optionId); Doc

 Collection<FieldConfigScheme> getAllRelatedSchemes(String optionId); Doc

 void assignProject(@Nonnull FieldConfigScheme priorityFieldConfig, @Nonnull Project project); Doc

 Set<Project> getProjectsWithScheme(@Nonnull FieldConfigScheme fieldConfigScheme); Doc

 void unassignProject(@Nonnull FieldConfigScheme scheme, @Nonnull Project project); Doc


We're also adding new events for whenever a priority scheme is created, updated, or deleted.

ClassnameEventJavadoc
com.atlassian.jira.issue.fields.config.manager.PrioritySchemeManager com.atlassian.jira.event.issue.fields.config.manager.PrioritySchemeCreatedEvent Doc

com.atlassian.jira.event.issue.fields.config.manager.PrioritySchemeDeletedEvent

Doc

com.atlassian.jira.event.issue.fields.config.manager.PrioritySchemeUpdatedEvent Doc

What's changing?

Some APIs also receive additional options, so that priorities are added or removed from priority schemes.

Show me the changes...
ClassnameMethod signatureChangeJavadoc
com.atlassian.jira.config.PriorityManager createPriority In addition to creating a priority, also adds this priority to the default priority scheme.Doc

 removePriority In addition to removing a priority, also removes this priority from all priority schemes.Doc

What's deprecated?

These APIs are deprecated, and replaced by the new PrioritySchemeManager class.

Show me the changes...
ClassnameMethod signatureReplacementJavadoc
com.atlassian.jira.config.PriorityManager setDefaultPriority

com.atlassian.jira.issue.fields.config.manager.PrioritySchemeManager

#setDefaultOption(FieldConfig, String)

Doc

 getDefaultPriority

com.atlassian.jira.issue.fields.config.manager.PrioritySchemeManager

#getDefaultOption(IssueContext)

Doc
com.atlassian.jira.config.ConstantsManager getDefaultPriority

com.atlassian.jira.issue.fields.config.manager.PrioritySchemeManager

#getDefaultOption(com.atlassian.jira.issue.context.IssueContext), or

com.atlassian.jira.issue.fields.config.manager.PrioritySchemeManager

#getDefaultOption(com.atlassian.jira.issue.fields.config.FieldConfig)

Doc

Upgrade procedure

Note: Upgrade to a test environment first. Test your upgrades in your test environment before rolling them into production.

If you're already running a version of JIRA, please follow these instructions to upgrade to the latest version:

  1. Before you upgrade, we strongly recommend that you back up your installation directory, home directory, and database.
  2. Read the release notes and upgrade guides for all releases between your version and the latest version.
  3. Download the latest version of JIRA Service Desk.
  4. Follow the instructions in the Upgrade Guide.

Upgrading from earlier versions?

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

  • 3.1, or later
    There are no known issues.
  • 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.
  • 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.9.
Last modified on Jun 26, 2020

Was this helpful?

Yes
No
Provide feedback about this article

In this section

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.