JIRA 5.1.7 Release Notes

15 October 2012

The Atlassian JIRA team announces the release of JIRA 5.1.7. This point release contains several updates and fixes.

Upgrading to JIRA 5.1.7 is free to all customers with active JIRA software maintenance.

Don't have JIRA 5.1 yet?

Take a look at all the new features in the JIRA 5.1 Release Notes and see what you are missing out on!

Upgrading from a previous version of JIRA

If you are upgrading, please read the JIRA 5.1.7 Upgrade Notes.

Updates and fixes in this release

JIRA 5.1.7 includes the following updates and bug fixes:

T Key Summary P Status
Bug JRA-29521 Making Workflow backups with a space behind will crash Workflowschemes and project associations High Resolved
Bug JRA-30290 Unexpected behavior by adding double question mark in the note message body when sharing an issue Medium Resolved
Bug JRA-28526 SQL Operations fail with Invalid column name error - 'watches' Medium Resolved
Bug JRA-26097 Bulk Edit assignee list performance limitation due to using CollectionList Medium Resolved
Bug JRA-30177 Issue Types for Scheme does not show when select issue type scheme for project Low Closed
Bug JRA-29992 NPE trying to get full name of deleted user Low Resolved
Bug JRA-29980 Issue content is spilling over into the right-hand column on View Issue Low Resolved
Bug JRA-29939 SQL Logger is failing to log SQL string for Statements with no bind variables Low Resolved
Bug JRA-29934 Default avatar is broken for instances that use Gravatar and are not publicly accessible Low Resolved
Bug JRA-29824 Performance problem when i create an issue with a version picker custom field Low Resolved
Bug JRA-28951 German translation of the dashboard contains underlined character Low Resolved
Bug JRA-28737 Setting jira.clone.prefix to null or blank results in a space added as a prefix Low Resolved
Bug JRA-28203 The free space graph in the system info is not correct Low Resolved
Bug JRA-27844 Import sub-tasks over already created issues doesn't work Low Resolved
Bug JRA-21843 Error displayed when accessing version workload report without logging-in Low Resolved
Bug JRA-19962 NullArgumentException Assertion thrown when navigating to shared dashboard via link when not logged in Low Resolved

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport