14 January 2011
JIRA 4.3 EAP 5 (a.k.a 4.3 milestone 5 or 'm5') is a public development release leading up to JIRA 4.3. An Early Access Preview (EAP) release is 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.
- A note for the curious: we skipped the EAP 4 release due to the holiday season.
The Atlassian team is proud to bring you the JIRA 4.3 EAP 5 release. Thank you for your feedback so far, and please keep providing it 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.
Dashboard Publish/Subscribe with Confluence (i.e. Gadgets 2.0) is also included, so if you are using Confluence as well as JIRA, your Confluence gadgets will now appear in the JIRA Gadget Directory (and vice versa).
Note to developers: JIRA 4.3 EAP 5 includes Unified Application Links (UAL), Gadgets 2.0, and 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.
Upgrading to JIRA 4.3 EAP 5
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 5
Add another application's Gadgets to your JIRA Gadget Directory
JIRA 4.3 EAP 2 includes Atlassian Gadgets 2.0, allowing you to quickly add all gadgets from your Confluence, Bamboo, FishEye or Crucible instance — or from another JIRA instance — to your JIRA Gadget Directory, for easy addition to your JIRA dashboard:
In the JIRA Gadget Directory , you can now click 'Gadget Subscriptions'. There you can provide the URL for the other application (or other JIRA instance), and all the gadgets from that instance will be added to your JIRA Gadget Directory.
Search the Change History with JQL 'WAS' Function (improved since EAP 3)
In EAP 2 we released 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':
Autocomplete has been implemented in EAP 5.
Full LDAP integration (upgrade note added since EAP 3)
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.
Note when upgrading from EAP 3
If you are upgrading to EAP 5 from EAP 3, please note that there have been changes to Crowd that require extra data in the cwd_application table.
You will need to update the table and add 'CROWD' into the application_type column:
(This will not be necessary when upgrading to the final release of JIRA 4.3.)
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.
Revamped User Avatars (new since EAP 3)
JIRA 4.3 introduces the new-look Atlassian avatars:
- User avatars are displayed as the icon for your profile, and to illustrate your comments on an issue. See the documentation on Adding a User Avatar.
We were fond of the old avatars, but think you'll agree they were looking a little dated by comparison:
Mail Server Configuration Improvements (improved since EAP 3)
In JIRA 4.3, administrators can now test their mail server configuration with the "Test Connection" button.
A 'Timeout' field has also been added in EAP 5.
New Plugin Management System
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
AppLinks pre-installed and configurable from the JIRA Admin UI
JIRA 4.3 EAP 5 includes Unified Application Links (UAL), so you no longer need to install it separately.
Application Links (AppLinks) is a plugin that allows you to link your JIRA, Confluence, FishEye, Crucible, Bamboo and Subversion applications. You can even choose to associate individual entities (i.e. JIRA projects, Confluence spaces, FishEye repositories, FishEye projects, Crucible projects, Bamboo projects) with each other. Applications Links is bundled with FishEye 2.4, Confluence 3.5, JIRA 4.3, and all later versions of those applications. In addition, Bamboo 3.1 is compatible with AppLinks. You can configure JIRA-to-Bamboo links via the JIRA administration screens.
Linking two applications allows you to share information and access one application's functions from within the other. For example, if you linked a JIRA server and a Confluence server, you could view JIRA issues in a Confluence page via the JIRA Issues Macro.
You also can associate entities of two linked applications. For example, you could associate a JIRA project with a Confluence space. This allows you to take advantage of additional integration features like link rendering, which lets you create links to issues or pages in the project or space using a simple textual reference, e.g.
[JRA-1234], [myConfluenceSpace:Test Page].
- In JIRA 4.3 EAP 5 there is now a 'Managed Unified Application Links' option on the 'Manage Project' screen, enabling you to easily configure application links for a given project.
For more about configuring Application Links, please see the Application Links Administrator's Guide.
Enhancements to Quick Search (improved since EAP 3)
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:
You can also find issues reported by you, another user or with no reporter, using the prefix "
r:" followed by a specific reporter term such as "
me", a username or "
none", such that:
r:me" — finds issues reported by you.
r:samuel" — finds issues reported by the user whose username is "samuel".
r:none" — finds issues with no reporter.
We are extremely pleased to announce that you should see a noticeable reduction in the time it takes to load a Dashboard.
- On average, dashboard performance has improved by 29%
- For large dashboards, the performance improvement is 35%
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.
Other Enhancements and Fixes
For the list of issues resolved in JIRA 4.3 so far, click here.