JIRA Core 7.6.x upgrade notes

Jira Core release notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Here are some important notes on upgrading to JIRA Core 7.6. For details of the new features and improvements in this release, see the JIRA Core 7.6 release notes

Upgrade notes

Priority schemes (UI changes)

Although we've made significant changes to how priorities are managed in JIRA, these changes won't affect your current configuration. Currently, your JIRA instance is 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. Until you create new schemes and make use of them (by associating with some projects), everything stays the same.

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

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


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


FieldConfig getFieldConfigForDefaultMapping(FieldConfigScheme fieldConfigScheme);


void delete(FieldConfigScheme fieldConfigScheme); Doc

FieldConfigScheme getScheme(Project project);


FieldConfigScheme getScheme(Long id);


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.

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.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


#setDefaultOption(FieldConfig, String)





com.atlassian.jira.config.ConstantsManager getDefaultPriority


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




Content-Security-Policy and X-Frame-Options headers

To prevent clickjacking, JIRA will add the X-Frame-Options and Content-Security-Policy security headers to each HTTP response. The headers will block the content from being embedded in iframes, which might also affect pages that you actually wanted to be displayed this way. If you embed any resources from JIRA on other sites (e.g. dashboards), they might not work after the upgrade. To fix this, you can either disable this feature, or choose resources to be excluded from receiving the security headers. Learn more

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 notes for all releases between your version and the latest version.
  3. Download the latest version of JIRA.
  4. Follow the instructions in the Upgrade Guide.

Upgrading from earlier versions?

  • 7.0, or later
    Take a look at the upgrade matrix. It lists known issues you should be aware of when upgrading between multiple versions.
  • Earlier than 7.0
    Consult the Migration hub. The JIRA 7.0 release introduced significant changes. You must first upgrade to JIRA 7.0 before upgrading to later versions.
Last modified on Dec 20, 2017

Was this helpful?

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