JIRA 4.0 Beta 1 Release Notes

JIRA 4.0 Beta 1 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.

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 1:

Thank you for your interest in JIRA 4.0 Beta 1

Download Beta

Upgrading to JIRA 4.0 Beta

JIRA 4.0 Beta can be downloaded here. Before upgrading, please refer to the JIRA 4.0 Upgrade Guide.

Highlights of JIRA 4.0 Beta 1

Advanced Searching

The new advanced search (JQL) provides support for logical operations (including AND/OR/NOT/NULL, even on custom fields) when filtering issues:

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


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 in to 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'):


Dashboard Gadgets

The new-look JIRA dashboard 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).

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 new gadgets are available in Beta 1:

  • 'Activity Stream' gadget (see below)
  • 'Create Issue' gadget
  • 'Filter Results' gadget
  • 'Issue Completed This Iteration' gadget

For optimal experience of the new dashboard, please use Firefox 3.x. Support for other browsers will be added prior to the launch of JIRA 4.0.


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.

See the documentation for more details.


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


Plus over 150 other fixes and improvements

Key T Summary P Status
JRA-5201 Bug Enable filter to specify more than 1 user Major Resolved
JRA-6164 Bug 'No Priority' count is not displayed in filter statistics portlet Major Resolved
JRA-6344 Bug Send to both previous and current assignees for all notifications Major Resolved
JRA-6550 Bug if text contains certain characters, cdata in xml based on this will be badly formed Major Resolved
JRA-8293 Bug Import fails if searchrequest:request data too large Minor Resolved
JRA-9048 Bug Calendar week begins with sunday independently from locale Major Resolved
JRA-10422 Bug Error in logs when nonexistent key used in wiki-rendered text Minor Resolved
JRA-10427 Bug Changing field descriptions in "Field Configurations" for custom fields does not work Major Resolved
JRA-10554 Bug Changing locale causes no translation change for 'Browse Projects' menu tab unless a project has been or is already selected Trivial Resolved
JRA-10854 Bug 'Restoring Data' Documentation incorrect or unclear Minor Closed
JRA-11933 Bug AutoTransitionListener - Reopen transition deletes issue summary Major Resolved
JRA-12165 Bug Unclear error message when bulk moving issues whose reporter cannot create issues Critical Resolved
JRA-12200 Bug Reporter system field throws ClassCastException after populateFromIssue() and validateFromParams() Major Resolved
JRA-12525 Bug Emails containing attachments with non-ASCII names lost Critical Resolved
JRA-12816 Bug OutOfMemoryError PermGen Space on Windows Func Test (under VMWare) Major Resolved
JRA-12976 Bug AbstractMessageHandler might not be removing spaces from email addresses before using them to determine if a user exists when creating an issue from an email Major Resolved
JRA-13003 Bug Moving portlet up reults in IndexOutOfBoundsException Minor Resolved
JRA-13011 Bug Component of a subtask is still component of original project after moving an issue Critical Resolved
JRA-13035 Bug CSV import can not import resolution date. Minor Resolved
JRA-13625 Bug Implicit profiling functionality broken Major Resolved
Showing 20 out of 724 issues Refresh


Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

6 Archived comments

  1. User avatar


    And still not able to rename users .. what a pitty

    02 Jun 2009
  2. User avatar


    yes that was exactly what I was looking for too - to rename users in my opinion should be a fundamental ability.

    02 Jun 2009
  3. User avatar


    Renaming users is easy!  All you have to do is to create an export xml file, shutdown your system - carefully hand edit the export file and replace all references to the username in question with the new one and bring up a new instance and import and voila!

    What you have to realize is that while it might *seem* simple to allow you to simply type in a text box and hit save, it's not! That's because they appear to have made the design decision not to use a surrogate key ( hidden userid ) for the user and so the username is copied everywhere in the data structures and is a nightmare to update.

    So quit your whining and understand the developers pain! :-)

    It's not as if you pay for the software or anything...

    02 Jun 2009
    1. User avatar



      04 Jun 2009
  4. User avatar


    Having recently changed my name, I have witnessed first hand the confusion caused when user records are keyed on username or other changeable data.  Some institutions have been able to make the change easily. Others, like Jira, use username, or name, or email or something else that can easily change. I have totally given up for some entities, and will just use my old name until I close the accounts.

    I have resolved, as a developer, to forevermore use a number for the primary key of any data that has a remote chance of being changed in the future.

    04 Jun 2009
  5. User avatar


    There were a JIRA 4 Enterprise Requirements Issue http://jira.atlassian.com/browse/JRA-11125. That is loveless copied to http://confluence.atlassian.com/display/JIRACOM/JIRA+Enterprise+Requirements, where the interest seems to have gone.
    Hopefully they will do some improvements on the SOAP-interface, that can help on administration quite a bit.

    12 Jun 2009
Powered by Confluence and Scroll Viewport