JIRA 6.3.3 Release Notes
Deep integration like never before
JIRA 6.3.3 now integrates deeper with your favorite code development toolsWith JIRA 6.1, we started a journey to help your developers visualize not just their issues, but all their work; their branches, their commits, and their reviews. We've now added the ability to link issue workflow and your development tools, giving increased visibility and allowing JIRA to automatically update issues as the work progresses.
But that's not all we've added in JIRA 6.3.3. We're still committed to improving efficiency and speed in JIRA, and we've added and improved features that'll allow you to be more productive. Download and say hello to faster, smarter development with JIRA 6.3.3 today.
JIRA's workflow engine is now source-code aware, so you can focus on the real work while JIRA automatically updates issues for you.
Instead of having JIRA issue statuses lagging behind, and the team not knowing the true state of the project, JIRA administrators can now configure triggers in JIRA workflows that respond to events in your linked development tools. For example, when a developer creates a branch to start work on an issue in Stash, the issue will automatically be transitioned from 'Open' to 'In progress' in JIRA.
JIRA responds to events in Stash, Bitbucket, FishEye and Crucible, as well as GitHub and GitHub:Enterprise.
Currently available events include:
Pull request created, merged, declined and reopened
Review started, summarised, approved, rejected, abandoned, closed
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 not only import data to create issues in bulk, but to also edit issues in bulk via a Comma-Separated Value (CSV) file import. This gives users the ability to create and edit issues using files in a CSV format, as well as using exported CSV data from a variety of systems and databases.
Inline image rendering
In our continued drive towards a more robust and efficient product, we've improved the way JIRA renders charts, removing the need to store temporary files on your system. Previously, JIRA would save a chart image in a temporary file on your system which it would then fetch to display in gadgets and reports. If for any reason the process was aborted, the partially rendered image remained in the temporary file. This could cause your temporary files to bloat, and in turn this would affect performance. By implementing a new method to render these images inline within the gadget or report, we've not only removed the need to store a temporary file for the image, but also streamlined the process by removing the need to make an additional request by JIRA. Working smarter means working faster.
Improved searching performance
We've implemented a change in the behaviour of searching. When querying large numbers of projects and issues with custom fields, JIRA previously had to decide what custom fields should be returned, and how. This process could take quite a long time, and searches were slow. Now, JIRA... will return columns for all the custom fields available, even if there are no values on those given issues. This has improved search performance dramatically, and solved JRA-25721 - Large number of projects and customfields causes performance degradation on the issue navigator Resolved .
JIRA Data Center Health ChecksNew for JIRA Data Center is a robust set of health checks so you can easily check the status and health of your enterprise JIRA instance. You can access the health checks in the Atlassian Support Tools section of your instance administration.
Known Issue with SQL Server
We do not recommend that customers running JIRA with SQL Server 2005/2008/2012 upgrade to JIRA 6.3.3. Please watch this issue JSW-14874 - DVCS Connector failed with SQLException: Incorrect syntax near the keyword 'MERGE' Resolved for workaround and upcoming fix information.
- JIRA 6.3 announced support for Java 8, and with JIRA 6.3.3 we have updated our embedded Java Runtime Environment (JRE) from 1.7 to 1.8 in our installers.
- Please review the End of Support Announcements for JIRA page for information about upcoming changes in JIRA 7.0.
- JIRA 6.3.3 also includes the following update and bug fixes.
The JIRA team
Jeroen De Raedt
Chung Park Chan
Andre Quadros Petry
Kuala Lumpur Support
Anna Monica Cardino
Azwandi Mohd Aris
Joe Wai Tye
John Chin Kim Loong
Viet Dung Nguyen
Voon Kiat Gan
Yew Teck En
Zulfadli Noor Sazali
San Francisco Support
Bryan J. Rollins
Product Marketing Management
Head of Development
Chris Le Petit
Was this helpful?
Thanks for your feedback!