JIRA 5.0.3 Release Notes

23 April 2012

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

Features and improvements in JIRA 5.0.3:


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

Upgrading from a previous version of JIRA

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

Invite users

If you're faced with the task of creating multiple users in your JIRA instance, you'll be happy to know that JIRA now includes the new Invite Users feature. This feature lets you email invitations that allow people to sign up to your JIRA instance. You just need a list of email addresses and a single click of a button.

'Autowatch' issues you create or comment on

A JIRA user who either creates a new issue or comments on an existing issue, will automatically become a watcher of that issue.

This feature applies to all new and existing JIRA users in a new (or upgraded) JIRA 5.0.3 installation.

JIRA users can easily disable this feature through their user profile by choosing Disabled for their Autowatch option when editing the Preferences section of their user profile.

Other improvements

Automatically suggested project keys

When creating a new project, the Add a new project dialog box now suggests a project Key based on the Name you specify.

Notify on my actions now disabled by default

By default, any new JIRA users will no longer be automatically notified of their own actions.

Individual users can change this option through their user profile by choosing Notify me for their My Changes option when editing the Preferences section of their user profile.

Better performance when mentioning users on issues

You should now see significant performance improvements when mentioning other JIRA users in an issue's Description or Comment field.

Character limits on issue fields can now be imposed

JIRA system administrators can now specify a character limit across description, environment and comment fields. Hence, when an issue is created, edited or commented on, if the content in one of these three field types exceeds this character limit, the user will not be able to save the issue or their comment until the character limit of the field is reduced below the limit.

This character limit is specified through the jira.text.field.character.limit property, which can be accessed through the Advanced Settings page in the JIRA administration area. Specifying a value of 0 (i.e. zero, which is the default value) for this property disables this feature.

New database monitoring page for JIRA system administrators

To help diagnose performance problems in JIRA associated with database connectivity, JIRA system administrators now have access to the new Database Monitoring page, which shows a graphical representation of JIRA's database connection usage over time.

JIRA system administrators can access this page by selecting Administration > System > Monitoring which opens the Database Monitoring page below.

(tick) Keyboard Shortcut: g + g + start typing monitoring

Don't have JIRA 5.0 yet?

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

Updates and fixes in this release

JIRA 5.0.3 includes the following updates and bug fixes:

Loading
T Key Summary P Status
Bug JRA-27743 Make the new limit for text fields limitable, by default OFF and configurable on the advanced config page Highest Resolved
Bug JRA-27777 Field restrictions on BaseURL too tight High Resolved
Bug JRA-27760 Bundle newest JIM (which is compatible with new Add Project dialog) High Resolved
Bug JRA-27343 Issue summaries containing newlines produce corrupted "Share" emails High Resolved
Bug JRA-25450 Pluggable web panels are not really reloadable within JIRA High Resolved
Bug JRA-24623 The size of description fields should be able to be limited High Resolved
Bug JRA-27909 Update Spanish Translations for JIRA 5.0.3 Medium Resolved
Bug JRA-27826 Arrow keys, SPACE, and Page Up/Down are not passed to contentEditable elements in the view-issue page Medium Resolved
Bug JRA-27668 The text length of a comment should be limited Medium Resolved
Bug JRA-27635 Slow requests can cause invalid user suggestions to be made from the comment (description) field Medium Resolved
Bug JRA-27631 Slow request can cause enter to delete text in the comment field if I have entered in an @ symbol Medium Resolved
Bug JRA-27628 The comment field can poll the server for users even when no @ symbols need to be processed. Medium Resolved
Bug JRA-27604 OAuth dance is happening too frequently between EAC and JAC or JDOG and JAC Medium Resolved
Bug JRA-27581 Upgrade of evaluation licence during setup wizard results in system error Medium Resolved
Bug JRA-27574 AJS.conglomerate.cookie can be written with invalid data that prevents other Atlassian applications from logging in. Medium Resolved
Bug JRA-27555 Cached user properties data becomes stubbornly stale after 30 min Medium Resolved
Bug JRA-27504 Disabled frother controls are not disabled enough Medium Resolved
Bug JRA-27500 jira-quick-edit-plugin hides the 'e' keyboard shortcut Medium Resolved
Bug JRA-27476 Share dialog does not stalk Medium Resolved
Bug JRA-27370 Unassigned Issues will get Assigned when Editing the Issue Medium Resolved
Showing 20 out of 37 issues Refresh

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