JIRA 4.3.1 Release Notes

1 April 2011

The Atlassian JIRA team announces the release of JIRA 4.3.1. This point release contains several updates and fixes, plus version 2.1 of the JIRA Importers Plugin, providing improved support for Bugzilla. Please see the documentation: Importing Data from Bugzilla.

JIRA 4.3.1 now supports anonymous binding when connecting to LDAP directories. Hence, when configuring an LDAP directory or an internal directory with LDAP authentication for user management in JIRA, you do not need to specify a Username and Password for JIRA to access your LDAP directory.

Notes for plugin developers:

  • JIRA 4.3.1 resolves a Jersey-related issue that was preventing the building of plugins against 4.3.
  • JIRA 4.3.1 provides backwards compatibility for the JavaScript Namespace Changes listed in the Plugin Developer Notes for JIRA 4.3.

The version of Tomcat included in JIRA 4.3.1 Standalone has been updated to Tomcat 6.0.32.

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

Don't have JIRA 4.3 yet?
Take a look at all the new features in the JIRA 4.3 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 4.3.1 Upgrade Guide.

Updates and Fixes in this Release

JIRA 4.3.1 includes the following updates and bug fixes:

T Key Summary P Status
Bug JRA-24138 JIRA startup can fail non-deterministically with NullPointerException High Resolved
Bug JRA-23886 Web sudo setting is cached High Resolved
Bug JRA-23876 Plugin System upgrade tasks should not be run before JIRA's own upgrade tasks are run High Resolved
Bug JRA-23846 Jersey 1.0.3 in JIRA 4.3-RC1 High Resolved
Bug JRA-23756 resource leakage and misleading log message when a bundled plugin gets upgraded High Resolved
Bug JRA-23595 Upgrade Task for labels can initially fail but then pass on second run with out converting a lot of the data High Resolved
Bug JRA-22633 JIRA starts up in unworkable stage if core plugin is not started High Resolved
Bug JRA-24143 When upgrading plugins that provide plugin points, the clients don't come up properly Medium Resolved
Bug JRA-23946 Failed jira.home startup check leaves JIRA broken Medium Resolved
Bug JRA-23926 XSRF token broken when you edit an Issue Type Scheme Medium Resolved
Bug JRA-23887 User Directory page shows 500 page after session timeout Medium Resolved
Bug JRA-23858 Upgrade path for delegated LDAP locks out internal JIRA users Medium Resolved
Bug JRA-23824 two dimensional filter gadget: link to subset contains wrong filter Medium Resolved
Bug JRA-23819 LDAP anonymous bind is not allowed in JIRA v4.3 Medium Resolved
Bug JRA-23763 UAL Trusted apps dialog misleads a user trying to log into another system if they are not a sys admin Medium Resolved
Bug JRA-23551 fault JQL searches created for Label Custom Fields within 2-dimensional statistic gadget and others Medium Resolved
Bug JRA-23522 edit-searcher/search-radio.vm [line 10,column 16] : ${checked} is not a valid reference. Medium Resolved
Bug JRA-22431 Decimal estimate time prevents saving of edited issues Medium Resolved
Bug JRA-22397 DefaultOSWorkflowConfigurator.JiraTypeResolverDelegator should fall back to JiraUtils.loadComponent(objClass) to load the class if type resolver is not found Medium Resolved
Bug JRA-20286 Date resolved is updated whenever resolution is included in transition screen Medium Resolved
Showing 20 out of 35 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