JIRA 6.4 Upgrade Notes
Please follow the instructions in the general Upgrading JIRA guide, as well as the JIRA 6.4 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.
This page also describes known issues as well as changes you should be aware of before deciding whether or not to upgrade to JIRA 6.4.
On this page:
Information for JIRA developers
See Preparing for 6.4 for important information that could affect your add-ons or scripts. Also, see our Java API policy for JIRA.
Upgrading to JIRA 6.4
Do you use Stash?
JIRA 6.4 launched with a known compatibility issue with Stash versions 3.4.3 to 3.7.1, which prevents the user management synchronisation from working. This will only affect you if you use JIRA to manage your users in Stash and will be fixed in JIRA 6.4.1. You can track progress by following these issues: JRA-42566 - Getting issue details... STATUS and STASH-7195 - Getting issue details... STATUS .
End of support for Jelly Scripts
JIRA 6.4 does not support Jelly scripts. If you are using Jelly scripts with JIRA, we recommend you move to Groovy Script Runner or the JIRA Command Line Interface, which will provide you with more flexible options. For more information, please see this page.
Enabling drag and drop attachments
If you have previously installed and used the JIRA Drag and Drop Attachment plugin, you will be pleased to know that this is now bundled with JIRA 6.4. To ensure your users retain the same experience, you will need to enable the feature:
- Login as an administrator and go to [your-instance-name].atlassian.net/secure/SiteDarkFeatures!default.jspa
In the Enable Dark Feature text field add
jira.plugins.dnd.attachment- This will enable the drag and drop attachments plugin for your users
Change to project creation
Creating a new project now creates a project-specific issue type scheme, workflow scheme, screen scheme and issue type screen scheme for that project. This change applies to all project types, except for the 'JIRA Default Schemes' project type, which still uses the shared default JIRA schemes when used to create a new project.
In particular, if you now want to create an Agile project ("Agile Software Development — Scrum" or "Agile Software Development — Kanban") which does not have project-specific schemes, you will need to do either of the following:
- Create a new project using the "JIRA Default Schemes" project type and manually create the board for the project,
OR - Create a new project using the "Agile Software Development — Scrum" or "Agile Software Development — Kanban" project type and re-associate the project with the JIRA default shared schemes (i.e. issue type scheme, workflow scheme, screen scheme and issue type screen scheme).
Upgrading to JIRA 6.4 from JIRA 6.1.x or earlier
In addition to the points listed above, please read the Important Version-Specific Upgrade Notes for every version of JIRA you are skipping.
Note, you cannot upgrade from JIRA 4.3.x or earlier, directly to JIRA 6.4. You must upgrade to an interim version first. See Skipping Major Versions When Upgrading JIRA.