Documentation for JIRA 4.3. Documentation for other versions of JIRA is available too. 
![]()
18 November 2010
JIRA 4.3 EAP 1 (a.k.a 4.3 milestone 1 or 'm1') is a public development release leading up to JIRA 4.3. For all production use and testing of JIRA, please use the latest official release.
Do not use in production
EAP releases should not be used in production environments as they are not officially supported.
Please also take note of the following information:
The Atlassian team is proud to bring you the JIRA 4.3 EAP 1 release. Development work on JIRA 4.3 has only commenced very recently, but we want your involvement from the earliest days. Please provide feedback here.
Note to developers: JIRA 4.3 EAP 1 includes Atlassian Plugin Framework version 2.6. Also please see the Plugin Developer Notes for JIRA 4.3, plus note that the REST API will continue to evolve through the 4.3 EAP releases — please watch the JIRA blog for the latest news on the REST API.
Highlights of JIRA 4.3 EAP 1:
Thank you for your interest in JIRA 4.3 EAP 1
Download EAP
Upgrading to JIRA 4.3 EAP 1
JIRA EAP releases are available here. Please follow the JIRA 4.3 Upgrade Guide.
The way users and groups are stored and accessed in JIRA has been totally rewritten in Release 4.3. This provides a number of additional capabilities, mainly the ability to use an LDAP server for all user information. Key features are:
In JIRA 4.3, administrators can now manage external User Directories directly from the JIRA Administration screens. Gone are the days of manually editing XML files.
In JIRA 4.3, administrators can now test their mail server configuration with the "Test Connection" button.
We have improved discoverability of issues and projects through the REST API: there is now a search resource, which can be used to search for issues using JIRA Query Language (JQL). It is also possible to obtain a list of projects in a JIRA instance. Have a look at the reference documentation to see if the REST API offers the features that you want (let us know if not).
Clients that log in through the REST API can now determine when the login has been denied due to a CAPTCHA requirement: the HTTP header X-Authentication-Denied-Reason has all the necessary information.
For the list of issues resolved in JIRA 4.3 so far, click here.