JIRA 4.3 EAP 2 Release Notes

7 December 2010

JIRA 4.3 EAP 2 (a.k.a 4.3 milestone 2 or 'm2') is a public development release leading up to JIRA 4.3. An Early Access Preview (EAP) release is a a snapshot of our work in progress, primarily focused on allowing JIRA users to see the new features in advance and provide us with some useful feedback. It also gives plugin developers an opportunity to test and fix their plugins in advance of an official release. For all production use and testing of JIRA, please use the latest official release.

The Atlassian team is proud to bring you the JIRA 4.3 EAP 2 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.

Identity management comes of age in JIRA 4.3, with complete LDAP integration. Additionally, you now have the ability to search an issue's change history. JIRA 4.3 also includes the Universal Plugin Manager for easier management of plugins.

Note to developers: JIRA 4.3 EAP 2 includes the 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 Developer blog for the latest news on the REST API.

Highlights of JIRA 4.3 EAP 2:

Thank you for your interest in JIRA 4.3 EAP 2
Download EAP

Upgrading to JIRA 4.3 EAP 2

JIRA EAP releases are available here. When upgrading, please follow the JIRA 4.3 Upgrade Guide.

Do not use in production

  • 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.

Highlights of JIRA 4.3 EAP 2


Search the Change History with JQL 'WAS' Function (new since EAP 1)

In EAP 2 we are releasing the first cut of Change History searching. There is much more functionality to follow, but for now you can search for changes to the Status field.

For example, the following will return all issues that currently have, or previously had, a status of 'In Progress':

status WAS "In Progress"

Note that autocomplete has not yet been implemented, but full error reporting is supported.



Full LDAP integration (Crowd 2.1 connectivity is new since EAP 1)

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
  • Ability to connect to a Crowd server for user management — Previous functionality
  • Ability to manage users fully within JIRA — Previous functionality
  • Ability to use 2 or more LDAP and/ or Crowd servers simultaneously for user management.



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.



Mail Server Configuration Improvements

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



New Plugin Management System (new since EAP 1)

JIRA 4.3 includes the Universal Plugin Manager (UPM), which provides you with a simple way of adding and managing plugins:

  • Auto-discovery of available plugins (see Featured Plugins in the screenshot below)
  • Point-and-click installation — no more downloading JAR files and restarting JIRA



Quick Search now has a Wild Card (new since EAP 1)

When using Quick Search to find issues with a particular version, you can now use the wildcard symbol: "". For example, "ff:3.2" will match any issue whose Fix For Version is:

  • 3.2
  • 3.2-beta
  • 3.2.1
  • 3.2.x



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, and to create links between issues.

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.

Have a look at the reference documentation to see if the REST API offers the features that you want (let us know if not).


Other Enhancements and Fixes

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


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