Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata


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

Icon

EAP releases should not be used in production environments as they are not officially supported.

Please also take note of the following information:

Icon
  • EAP Releases are Not Safe— EAP releases are snapshots of the ongoing JIRA development process. As such:
    • While we try to keep these releases stable, they have not undergone the same degree of testing as a full release.
    • Features in development releases may be incomplete, or may change or be removed before the next full release.
  • No Upgrade Path — Because EAP releases represent work in progress, we can not provide a supported upgrade path between EAP releases, or from any EAP to the eventual final release. Thus, any data you store in a JIRA EAP release may not be able to be migrated to a future JIRA release.

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

Icon

JIRA EAP releases are available here. Please follow the JIRA 4.3 Upgrade Guide.

Highlights of JIRA 4.3 EAP 1

 

Full LDAP integration

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:

  • Ability to connect to an LDAP server, including to Microsoft Active Directory, for user management. This includes:
    • Read-write access
    • Read-only access
    • Read-only access with local groups
    • Use LDAP for authentication only — Previous functionality

^Top

 

User Directory management via JIRA Admin UI

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.

^Top

 

Mail Server Configuration Improvements

In JIRA 4.3, administrators can now test their mail server configuration with the "Test Connection" button.

^Top

 

REST API improvements

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.

^Top

Other Enhancements and Fixes

For the list of issues resolved in JIRA 4.3 so far, click here.

^Top

  • No labels

2 Comments

  1. Anonymous

    Will I no longer need to purchase my Crowd license once this version of JIRA is released?

    1. If all you use Crowd for is to get good LDAP for JIRA, then with the release of JIRA 4.3 you won't need Crowd anymore.

      If you're integrating lots of custom applications or want SSO, you'll still want Crowd.

      We'll get a full FAQ out early next year.