This page last changed on Sep 14, 2010 by ggaskell.
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.
A Beta release is a preliminary release leading up to the official release of a JIRA version. Beta releases are a snapshot of our work in progress and provide an advance preview of new features to the general public. JIRA plugin developers can also use Beta releases to test and fix their plugins in advance of an 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.
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.
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 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.
"Pie Chart" report and gadget — Shows the search results from a specified issue filter (or project) in a pie-chart, based on a statistic of your choice.
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. ^Top
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.
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.
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.)