JIRA 5.1 : JIRA 4.4.2 Release Notes

JIRA 4.4.2 has a critical issue (JRA-25914) which may cause data corruption. You may wish to wait until JIRA 4.4.3 is released before upgrading JIRA.

12 October 2011

The Atlassian JIRA team announces the release of JIRA 4.4.2. This point release contains new features that give users more JQL enhancements to filter issues based on system fields that possessed a specified value at some point in the past, in addition to several updates and fixes.

 

 

Features and improvements in JIRA 4.4.2:

Thank you for your feedback:

More than three new features/improvements implemented
Over 420 votes fulfilled

Your votes and issues help us keep improving our products, and are much appreciated.

JIRA 4.4.2 is of course free to all customers with active JIRA software maintenance.

 

Upgrading from a Previous Version of JIRA

If you are upgrading, please read the JIRA 4.4.2 Upgrade Notes

More Enhancements to JQL — New "CHANGED" Operator and "WAS" Improvements

Enhancements were introduced in JIRA 4.4.0 that allowed you to search the history of an issue's Assignee and Reporter fields.

In JIRA 4.4.2, JQL supports the new "CHANGED" operator, which can accept the optional predicates "FROM", "TO", "ON", "DURING", "BEFORE", "AFTER" and "BY".

For example, the following JQL query:

status changed FROM "In QA Review" to "QA Rejected" BY freddo BEFORE endOfWeek() AFTER startOfWeek()

Will find any issues whose Status field value was at some point "In QA Review" but changed to "QA Rejected", by user 'freddo', and after the start and before the end of the current week.

You can use complex queries such as these to generate the following 'Single Level Group By Report', which in the example below, shows grouping by 'Team'.

The "CHANGED" operator can be used on the Status, Assignee, Priority, Reporter, Resolution and Fix Version fields.

The "WAS" operator can be used on the Fix Version field too. For example, the following JQL query:

fixVersion WAS 4.4

Will find any issues whose Fix Version field was at some point (or currently is) set to 4.4.

Other Improvements

  • Mixed-case LDAP usernames are now treated as the same user when conducting searches in JIRA (JRA-24558).
  • When a new user is added to JIRA, JIRA will only add that user to groups which explicitly have the 'JIRA Users' global permission. JIRA no longer adds new users to nested groups of a group that has the 'JIRA Users' global permission, unless those nested groups also explicitly have this permission (JRA-25554).
  • The Application Links Link Rendering plugin, which was broken when JIRA 4.4 was released, is now fixed and is compatible with all JIRA 4.4.x versions (JRA-25594).
  • GreenHopper 5.7.4 is now bundled with JIRA 4.4.2.

Don't have JIRA 4.4 yet?

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

Updates and Fixes in this Release

JIRA 4.4.2 includes the following updates and bug fixes:

JIRA Issues (34 issues)
Type Key Summary
Improvement JRA-5536 Search the change history
Bug JRA-24558 JIRA using mixed-case username from LDAP corrupt other features
Bug JRA-25406 JIRA 4.4 Custom field multiuser picker will generate error in XML views
Bug JRA-25547 Issue statistics are now incorrect for multi-select fields
New Feature JRA-24650 Expand "WAS" JQL operator to support fixVersion
Bug JRA-23861 An admin can lock themselves out of JIRA by changing the order of the User Directories.
Bug JRA-25688 Big database performance hit in JIRA 4.4.1
Bug JRA-25412 The "Event" is no longer displayed in the subject of text format emails.
Bug JRA-25395 Invalid Date Format Error At Issue Navigator After Change User Prefer Language
Bug JRA-23696 German translation for work ratio overflows in Searchview sidebar
Bug JRA-25668 Progress Indicator when converting custom fields during 4.4 upgrade
Bug JRA-25594 Update Applinks-linker to work with JIRA 4.4
Bug JRA-25554 When creating a new user, new account is added to all nested group of jira-users
Bug JRA-25497 failed upgrade to new user management due to missing osuser.xml
Bug JRA-25288 Email received in different language if the sender has different language preference
New Feature JRA-15819 record issue resolver
Bug JRA-25611 Unable to modify group memberships for re-created users
Bug JRA-25541 Infinite loop in group picker
Bug JRA-24918 'Test Settings' in User management needs perform more complete connection validation
Bug JRA-24425 issue settings translation not working
Bug JRA-25765 Bundle latest QE/QC plugin with JIRA 4.4.2
Bug JRA-25751 Add warning to the atlassian-feedback-plugin that feedback goes to Atlassian
Bug JRA-25750 Update AO plugin to 0.17 in 4.4.2
Bug JRA-25692 Upgrade fisheye plugin to 3.4.5 to ship in JIRA 4.4.2
Bug JRA-25571 Uploading a plugin update through UPM does not run upgrade tasks
Bug JRA-25358 round trips between advanced and simple search with multiple label custom field search
Bug JRA-25297 Add net.java.ao.sql to log4j.properties in JIRA
Bug JRA-25237 JPG image causes JIRA to not display attachments in web UI and REST API
Bug JRA-25192 The list of roles in a project can be invalid after a project import
Bug JRA-24978 Remove the Sybil code in AbstractIssueSelectAction that causes multiple reads to the database when we have already done it
Bug JRA-24946 Link LDAP integration errors to a cac page helping customers to troubleshoot integration issues
Bug JRA-24945 Include Directory Configuration Summary from User Directories in System Info
Bug JRA-24634 Delegated LDAP UI does not include the "Follow Referrals" option
Bug JRA-17466 DefaultPortalPageManager should use index to find portal pages by owner and name

Attachments: