Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

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

Icon

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

Please also take note of the following information:

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

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

^Top

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.

^Top

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.


^Top

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.

^Top

Project Icons

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

^Top

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.

^Top

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.

^Top

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

^Top

Plus over 150 other fixes and improvements

Loading
Showing 20 out of 981 issues Refresh

^Top

  • No labels

6 Comments

  1. Anonymous

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

  2. Anonymous

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

  3. Anonymous

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

    1. Anonymous

  4. Anonymous

    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.

  5. Anonymous

    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.