JIRA 6.4 EAP 14 (m14)
12 February 2015
Atlassian is proud to present JIRA 6.4 EAP 14 (m14). This public development release is part of our Early Access Program (EAP) leading up to the official JIRA 6.4 release. We are making these EAP milestones publicly available so that developers can start assessing the impact of the changes that we are making.
In this release:
Redesigned Status Page
The Status administration page has been streamlined and is now much easier to read and use. As an added bonus, we've implemented a highly-voted feature request: the ability to define the order of statuses.
Go to Issues > Statuses in your administration console to try it out.
Updated priorities and resolutions
JIRA will now ship with a new set of priorities, and a new resolution. The old default priorities of Blocker, Critical, Major, Minor and Trivial will be replaced with Highest, High, Medium, Low and Lowest. If you are upgrading an installation of JIRA, or importing existing data, JIRA will respect your original priorities and they will continue to be available instead of the new priorities. The new priorities will only become available and therefore the default in new installations. And remember, if you want to change your priorities, JIRA admins are able to edit, add and delete priorities in JIRA by accessing the JIRA Administration menu > Issues > Priorities. We're also shipping with a new resolution of Won't Do. This resolution will only become available when you create a software development project in JIRA and is exactly the same as the current Won't Fix resolution, apart from the name! JIRA admins can also edit, add and delete resolutions through the JIRA Administration menu > Issues > Resolutions.
Change to project creation in JIRA
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 Classic' project type, which still uses the shared default JIRA schemes when used to create a new project. This change is to enable more flexibility around editing JIRA schemes on a per project basis.
Users can create issues in bulk
Previously, creating issues in bulk was only available to JIRA administrators. Now, we've given users the power and flexibility to import data to create issues in bulk via a Comma-Separated Value (CSV) file import. This gives users the ability to create issues using manually created files in a CSV format, as well as using exported CSV data from a variety of systems and databases. Simply click the Issues drop-down and select Import issues from CSV, and then follow the steps in the import wizard. Your new issues will be available shortly!
A leaner JIRA
We're constantly trying to improve our customer experience and we remove functionality if we feel it doesn't add value for our users. In this release of JIRA Server we've removed Scheme Tools, which were originally designed to assist administrators in moving users from groups (used in JIRA versions prior to 3.7) to project roles (from JIRA 3.7 forward). We've also removed the News Gadget.
To improve performance, we're in the process of reworking a lot of the dashboard gadgets, improving their efficiency and load times. You may notice some of the gadgets look slightly different too, we've given them a cosmetic make-over to align them with JIRA and our design principles.
More 'bulk edit' functionality
We've enhanced the ability to edit system multi-select fields when performing a bulk edit of issues. Previously, when you wanted to change the Affects Version/s, Fix Version/s, Component/s or Label/s fields, any changes you made would overwrite the existing values. This made it difficult to bulk edit these fields if they already held different values that you wanted to keep.
Now, you'll be able to select whether to you want to clear or add to all the existing values, replace all the existing values with a specific value or set of values, or simply remove a specific value or set of values. This added functionality has been widely requested, and we'll be happy to satisfy the numerous votes on issues such as:
JRA-24118 - The labels fields should be additive when doing bulk updates Resolved and
JRA-13456 - Bulk add to Affects Version/s Closed .
The two-dimensional filter statistic gadget
Due to a recent change in how we implemented the gadget, we removed the ability to click on the headers of the rows and columns to go to a issue list of that specific column or row. This functionality is now available by clicking the total for the required column or row. To make this consistently available, we've removed the ability to select whether you do or don't display the totals. The totals will now be displayed by default.
JIRA now has a workflow validator that will make sure that when you create or import workflows, you don't have statuses that can't be reached or exited. The validator will also tell you if you don't have the correct permission condition set up when you import a workflow. The validator is particularly useful in validating large, complex workflows.
Wiki Editor and image paste for issue descriptions and comments
We've made it easier to add wiki markup to issue's comments and descriptions by giving you a wiki editor within JIRA. This markup tool will automatically add the syntax for your text, making your descriptions and comments more informative. We've also added the ability to paste images into comments and descriptions directly from your clipboard using the keyboard shortcuts (CTRL + V for Windows users, CMD + V for Mac users).
Persistent custom field values
When you are creating an issue and check "Create another", the custom field values you entered will be retained for the next issue you create. When you close the Create issue dialog, the custom values will be reset. This resolves JRA-39981 - Custom fields not pre-populated after creating an issue with the 'create another' option RESOLVED for our customers.
Versions page - Background refresh
Development data is continually synchronised between JIRA and your development tools. JIRA will now perform a final check when you visit the JIRA Version Progress page and synchronise any data that is not up to date. A subtle indicator will show when issue data, including related warnings, is being refreshed. If you are looking at out-of-date information, you will be prompted to reload the page.
Versions page - Manage warnings
You can now manage the warnings to show or hide all warnings in a particular category. For example, you may want to hide the 'Unreviewed Code' warnings, if your team doesn't perform code reviews in a tool that is connected to JIRA.
HipChat Integration refinement
JIRA and HipChat integration has been reworked to improve the initial configuration, remove the need to edit project workflows and to improve the customization capabilities of linking projects to specific rooms.
- Improved integration - Initial integration has been improved with a simple to use configuration wizard that removes the need for obtaining and entering tokens significantly reducing the time it takes to link JIRA and HipChat.
- More refined room linking - Notifications can now be created and linked to rooms with the actions you want. Link individual projects to rooms and set notifications to be sent when an issue is created or changes status. In addition, you can configure notifications to be sent based on issue type and priority.
- Improved notifications - Notifications have been redesigned to allow you to quickly view your important issue information quickly without disrupting your workflow in HipChat.
Was this helpful?
Thanks for your feedback!