JIRA 4.0 Beta 3 Release Notes

August 27, 2009

JIRA 4.0 Beta 3 is a public development release leading up to JIRA 4.0. For all production use and testing of JIRA, please use the latest official release.

Do not use in production

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

Please also take note of the following information:

  • Beta releases are not safe— Beta 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 Beta releases represent work in progress, we cannot provide a supported upgrade path between Beta releases, or from any Beta to the eventual final release. Thus, any data you store in a JIRA Beta release may not be able to be migrated to a future JIRA release.

It is not possible to upgrade JIRA 4.0 Beta 1 or 2 data to Beta 3. The data needs to come from an already released JIRA version (for example, JIRA 3.13.5).

The only plugin that is compatible with JIRA 4.0 Beta is the latest JIRA Toolkit. Do not install any other plugins.

The Atlassian JIRA team is delighted to present a brand new version of one of the world's favourite issue-trackers.

Highlights of JIRA 4.0 Beta 3:

Thank you for your interest in JIRA 4.0 Beta 3

Download Beta

Installing/Upgrading to JIRA 4.0

JIRA 4.0 Beta 3 can be downloaded here. Before upgrading, please refer to the JIRA 4.0 Upgrade Guide. You will also need to go to my.atlassian.com and generate a "JIRA 4 Evaluation" license, as any existing 3.x license files will not work with 4.0 Beta 3.

Highlights of JIRA 4.0 Beta 3

Advanced Searching

The new advanced search (JQL) provides support for logical operations, including AND, OR, NOT, NULL, EMPTY --- even on custom fields:

For more on the new JQL search syntax, please see the documentation.


Dashboard Gadgets

The new-look JIRA dashboard not only looks awesome: it now uses industry-standard 'gadgets'. So you can add external gadgets to your JIRA dashboard, as well as displaying JIRA gadgets in other places (such as iGoogle).

You can easily customise your dashboard by choosing a different layout, adding more gadgets, dragging the gadgets into different positions, and changing the look of individual gadgets.

What's happened to your favourite JIRA portlets? Don't worry: every portlet that previously shipped with JIRA has been converted to a 'legacy gadget'. And if you are a plugin developer and have created your own portlets, see the instructions for converting your portlets to gadgets.

The following gadgets are available in Beta 3:

  • 'Activity Stream' gadget (see below)
  • 'Admin' gadget
  • 'Bamboo Plan Summary' gadget*
  • 'Bamboo Status' gadget*
  • 'Crucible Charting' gadget
  • 'Create Issue' gadget
  • 'Favourite Filters' gadget
  • 'Filter Results' gadget
  • 'FishEye Charting' gadget
  • 'Introduction' gadget
  • 'Issue Completed This Iteration' gadget
  • 'Login' gadget
  • 'Quicklinks' gadget
  • 'Voted Issues' gadget

* Requires Bamboo 2.3.2 Beta 1 or later.


Activity Stream

The new 'Activity Stream' gadget displays a summary of the latest activity in JIRA projects (and/or by particular people) in which you are interested.

The 'Activity Stream' gadget also provides an RSS feed, allowing you to create very specific RSS feeds of only the information that is most relevant to you.

See the documentation for more details.


Issue Actions in the Issue Navigator

By popular request, issues can now be actioned directly from the Issue Navigator:

The "Actions" menu is also available for the list of sub-tasks within an issue.

Charting Now Comes Standard

The following reports and gadgets from the Charting plugin have now been integrated into JIRA:

Also, the "Resolved" field from the Charting plugin is now part of JIRA, so every issue now automatically has its resolution date recorded.


New-look "Browse Project"

JIRA 4.0 provides a cleaner, more interactive view into a project:

See the documentation for more about browsing projects, versions and components.

Project Icons

You can now give your project a visual identity, thanks to the introduction of project icons ('avatars'):


New-look Header

The new-look JIRA header gives you quick access to all the most commonly-used functions. Creating an issue just got super-fast!

Click to zoom in:

If you prefer keystrokes rather than mouse-clicks, you'll be pleased to know that you can use your keyboard to navigate the new header menus.

Default Unit for Time Tracking

You can now specify your preferred Default Unit (minutes/hours/days/weeks) for your JIRA system. This will be applied whenever users log work on an issue without specifying a unit.


"History" is now permanent

Your list of recently-viewed issues is now stored in JIRA's database — so it's available after you log out and back in, even if you use a different machine.


Engine Room

Beyond the 'Back' Button

When navigating away from a page where you have modified data, you will be prompted to see if you would like to save the data or discard your changes (see JRA-14911).

Index Queue

Index updates are now put in a queue. So even if the update takes longer than 30 seconds, the operation remains on the queue and is not lost. (See JRA-14220.)


Plus over 450 other fixes and improvements

Click here for full list.

Key T Summary P Status
JRA-16560 Bug Upgrading bunded plugins fails Highest Resolved
JRA-16685 Bug Enormous font on random pages Highest Resolved
JRA-16833 Bug Avatar Picker has layout issues while cropping Highest Resolved
JRA-17664 Bug Fix up upgrade tasks 402 and 410 to ensure that we don't iterate and update the same table at the same time Highest Resolved
JRA-17903 Bug Issue Navigator URL parameters should only support either JQL or old style params, but not both. Highest Resolved
JRA-17927 Bug view screen does not redirect to advanced properly when query doesn't fit and does not add validation errors when redirected in advanced more. Highest Resolved
JRA-17984 Bug Contents of Description field get lost if saved in preview mode Highest Resolved
JRA-17989 Bug Login gadget does not work under Safari 4.0.2 Highest Resolved
JRA-18176 Bug Getting an IO exception from the postgres driver when upgrading JAC data from the ResolutionDate upgrade task Highest Resolved
JRA-18492 Bug Ctrl A has been stolen by the Menu link guy. Windows users are not going to be happy Highest Resolved
JRA-18543 Bug System dashboard by default has project and quicklink gadget which is not shown at the time of first login but there is error in default dashboard setting. Highest Resolved
JRA-18626 Bug Application gives stack trace if user tries to create issue with JIRA running with expired evaluation key. Highest Resolved
JRA-18645 Bug Default attachments directory not created Highest Resolved
JRA-18650 Bug Scheduler and Mail Queue is being started during the Upgrade of data following a v1 license detection Highest Resolved
JRA-18654 Bug Project portlets do not respect categories on upgrades Highest Resolved
JRA-18692 Bug Drop down menus on JIRA trunk are not working Highest Resolved
JRA-18718 Bug UpgradeTask_Build418 updates PortletConfigurations while holding an open ResultSet Highest Resolved
JRA-18855 Bug Field Visibility for Fix Version not working correctly with issue type scheme (probably for all fields) Highest Resolved
JRA-19003 Bug User can't click on drop downs and select other preference options in IE Highest Resolved
JRA-19038 Bug JIRA Beta5 - cant get access to custom fields during startup Highest Resolved
Showing 20 out of 696 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