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

 

22 February 2012

The Atlassian team is proud to bring you JIRA 5.0.

Overview

JIRA 5.0 connects people, teams and applications. Users can share issues and search results with each other. They can also mention a colleague with '@username' in an issue to call their attention to an issue. Remote issue links connect JIRA issues to objects and pages in other web applications. Activity streams show events from all linked Atlassian applications and third-party apps.

Even further, JIRA 5.0's new APIs are designed for developers who want to connect JIRA to other applications:

  • New REST APIs to manage every facet of an issue.
  • New APIs for remote issue links and activity streams.
  • A stable Java API for JIRA.

Highlights:

Share issues and mention users

Rapidly create and edit issues



  • Create links to JIRA issues on another JIRA site
  • Create links to any URL
  • Create links via JIRA's Java or REST API
  • Share issues quickly with other users
  • Mention a user in an issue comment
  • The username or email address autocomplete as you type
  • Rapidly create and edit issues in a dialog box
  • Create multiple issues in succession
  • Customise to show fields you use most often

 

Upgrading to JIRA 5.0

Icon

JIRA 5.0 can be downloaded from the JIRA Download Center. Before upgrading, please refer to the JIRA 5.0 Upgrade Notes.

 

Note to developers: Please see Preparing for JIRA 5.0 on the Atlassian Developers site.

Highlights


Remote issue links

The remote issue links feature provides a powerful way to link JIRA issues to items external to your JIRA installation, residing on external applications.

Along with a Java and REST API to add these links, end users can also:

  • Add an issue link from a JIRA issue to an issue on another JIRA site, including reciprocal links between these issues.
  • Search for a Confluence page from a JIRA issue and add an issue link to that page.
  • Add an issue link from a JIRA issue to any web page URL, such as a page of documentation, a technical note, or any other page on another web site.

Check out a live example here.

If you are a:

  • JIRA user — see Linking Issues for details on using remote issue links within JIRA.
  • JIRA system administrator — see Configuring Issue Linking for details on how to make remote issue linking available to your users by setting up the required application links between JIRA and other applications.
  • JIRA developer — see JIRA Remote Issue Links on our developer documentation site.

^Top

 

Share issues and mention users

Screenshot: Sharing a list of issues with other users

Screenshot: Mentioning a user in an issue comment

Need someone else to take a look at a JIRA issue or a list of issues?

  • View any issue or a list of issues on the issue navigator, click the Share button at the top-right (or type s) and specify JIRA users (based on their names or user names) or any email address of people you want to share the issue with.

    Recipients will be emailed a link to the issue (or a list of issues 'shared' via the issue navigator).

(info) Please Note:

  • You require the Browse Users global permission to access the Share button or the 'suggested users' feature when 'mentioning' a user. However, if you know the username of a JIRA user, you can still mention them without this permission.
  • JIRA system administrators will need to configure JIRA's outgoing SMTP mail server for the 'share' and 'mentions' features to work.

^Top

 

Rapidly create and edit issues

JIRA 5.0 lets you create and edit issues and sub-tasks much faster. Creating and editing is now performed in a dialog box (rather than a separate form), so that you do not need to leave the current page or have it reload just to start creating or editing an issue or sub-task.

You can customise fields on the Create Issue/Edit Issue dialog boxes by removing or adding fields fields through the Configure Fields button. JIRA remembers your last set of field choices, giving you a personally customised dialog box that presents you with your most commonly used fields whenever you create or edit an issue.

The Create Issue dialog box allows you to rapidly create a series of related issues with similar options. When you select the Create another check box before clicking the Create button, JIRA creates your issue and automatically pre-populates a new Create Issue dialog box with your previous field values, whilst leaving the Summary field blank. Be aware that any attachments attached to your previously created issue are not carried across by this feature.

The Assignee, Project and Issue Type fields use 'autocompletion' too. Hence, you no longer a need to scroll through a whole raft of items to specify these fields when creating or editing an issue.

You can easily access these dialog boxes by typing 'c' to create an issue, or 'e' from a selected issue on the issue navigator or 'view issue' page to edit that issue.

^Top

 

Search for issues based on their history

'CHANGED' operator introduced

Introduced in JIRA 4.4.3, JQL's CHANGED operator can accept the optional predicates FROM, TO, ON, DURING, BEFORE, AFTER and BY, and can be used on the Status, Assignee, Priority, Reporter, Resolution and Fix Version fields.

For example, this link shows all the issues logged against the JIRA project on our 'jira.atlassian.com' site, whose Fix Version field was changed to "5.0".

You can also create more complex JQL queries with the CHANGED operator by fine-tuning them with predicates. For example, the following JQL query:

will find any issues whose Status field value was at some point "In QA Review" but changed to "QA Rejected", by user freddo between the start and end of the current week.

You can use complex queries such as these to generate the 'Single Level Group By Report' in the screenshot above, which shows grouping by Team.

'WAS' operator enhanced

Also introduced in JIRA 4.4.3 was the ability of the WAS operator to work with the Fix Version field. For example, the following JQL query:

Will find any issues whose Fix Version field was at some point (or currently is) set to 4.4.

^Top

 

Activity streams now show activity from other applications


Screenshot: Activity stream gadget showing activity
from other Atlassian applications

Screenshot: Activity stream gadget showing activity
from non-Atlassian applications

We have expanded the Activity Stream features introduced in JIRA 4.4 with:

  • The ability to show external activity from another Atlassian application (such as Confluence, FishEye/Crucible and Bamboo) via an Application Link.
  • The ability to combine this external activity into an Activity Stream gadget on a JIRA dashboard.
  • An API for creating entries in activity streams from remote applications via the REST API or locally via Java.

Refer to the Preparing for JIRA 5.0 section of our developer documentation site for more details.

With these new features, you can:

  • See Confluence page updates from your activity streams in JIRA, then drill down into those Confluence pages for more information.
  • See updates from another JIRA site. For example, activity streams on your development team's JIRA site (behind the firewall) can include activity on your support team's customer facing JIRA site.

^Top

 

Manage other users' shared filters and dashboards

Introduced in JIRA 4.4.1, JIRA administrators have the ability to change the ownership of or delete other user's shared filters and dashboards. A shared filter or dashboard is a filter/dashboard created (and hence, owned) by a user, which the user has then shared with others.

Since JIRA only allows the editing or modification of shared filters/dashboards by their owners, this new JIRA feature is especially helpful in situations where a user has left an organisation, but the shared filters or dashboards they created continue to be used by others within the organisation.

You can access these features by selecting Administration > Users > Shared Filters or Shared Dashboards (or using the keyboard shortcut g + g + start typing shared filters or shared dashboard).

On the 'Shared Filters' or 'Shared Dashboard' pages, you can search for any shared filters/dashboards, or use the cog icon to change the owner of a shared filter/dashboard to another user or delete the shared filter/dashboard.

(info) Only users with the Create Shared Objects global permission can share their filters and dashboards with other JIRA users.

^Top

 

Administration user interface improvements

Following on with improvements to the Administration User Interface (UI) in JIRA 4.4, JIRA 5.0 provides further improvements to the Administration UI by converting forms on various Administration pages to convenient dialog boxes.

For example, the form for adding users is now a dialog box, which is accessed by clicking Add User on the Users page of JIRA's Administration area.

In addition to the dialog box for adding a new user, the 'Attachments' and 'Workflows' pages have been redesigned and the forms associated with these pages have been converted into convenient dialog boxes too.

^Top

 

REST API (with tutorials) for working with issues in JIRA

JIRA's REST API has undergone a significant number of changes and improvements to provide the following:

  • Create new issues.
  • Retrieve metadata for creating new issues and editing existing ones.
  • Delete existing issues and their subtasks.
  • Create remote 'issue links'.
  • Retrieve metadata from your favourite filters and dashboards.
  • Retrieve metadata about your permissions.
  • Almost all system fields and JIRA's built-in custom field types are supported.

(info) Please also note that the we have changed the api-version name component of URLs for JIRA's REST API calls from '2.0.alpha1' to simply '2' (or 'latest' to use the latest REST API version available with your version of JIRA).

Refer to the Preparing for JIRA 5.0 section of our developer documentation site for more details.

We also have a series of REST API Tutorials to help you get started using our new REST API improvements.

(info) You might also want to try out Atlassian's new REST API Browser, which is available in the Atlassian Plugin SDK and can be accessed by adding /plugins/servlet/restbrowser#/user/search to the end of the URL for accessing JIRA (e.g. http://localhost:2990/jira/plugins/servlet/restbrowser#/user/search) within the SDK environment.

^Top

 

Stable Java API

JIRA's Java API has undergone a significant number of changes and improvements to provide the following:

  • More stability and compatibility with future versions of JIRA. See our Java API Policy for JIRA for details.
  • Removal of deprecated OSUser classes.
  • Removal of deprecated portlets (replaced by gadgets in JIRA 4.0) and their related APIs.

Refer to the Preparing for JIRA 5.0 section of our developer documentation site for more details.

If you are developing plugins for JIRA 5.0, please also check out our newly published set of JIRA plugin tutorials.

^Top


 

New troubleshooting and debugging tools

JIRA 5.0 adds several tools to help Administrators debug the configuration of their instance.

  • A number of email debugging tools are now provided to System Administrators in the new Logging and Profiling page under Troubleshooting and Support
    • Enable or disable mail logging
    • Turn debug mail logging on or off
    • Configure a logging level for a new package easily in the default loggers section.
  • For testing and troubleshooting LDAP connections, much more comprehensive testing is now provided, including basic connections, user retrieval, user membership, group retrieval, group membership and authentication.

^Top

 

New email handler wizard

JIRA 5.0 incorporates a new mail handler wizard that greatly simplifies the process of configuring incoming mail handlers for creating issues or comments from email messages.

There is no longer a need to configure a JIRA service and enter a complex string of mail handler parameters to handle your email messages. Instead, simply you configure your mail handler through a convenient wizard.

Improvements have been made to the layout of JIRA's mail configuration options. The configuration options in the Mail Servers administration page have been separated into two separate pages — one for Outgoing Mail (SMTP) and another for Incoming Mail (POP/IMAP) configurations. The configuration options for mail handlers have been moved from the Services administration page and incorporated into the Incoming Mail page.

^Top

 

Enhancements to the 'view issue' page

The 'view issue' page has the following enhancements:

  • The Issue Links section of the 'view issue' page has been redesigned to cater for remote issue links (above) and makes better use of space — the separate line used to group issue link types in earlier versions of JIRA has been removed.
  • The right-hand side of the view issue page now uses a fixed width. Hence, when the 'view page' is maximised on large, high resolution monitors, the association between field names and values is not lost.
  • In JIRA versions prior to 5.0, initially clicking any tab in the Activity section would reload the whole 'view issue' page. In JIRA 5.0, the content within each of these (non-selected) tabs only loads upon being clicked by a user and does so independently of the rest of the 'view issue' page. This modified behaviour provides more rapid access to the information on these tabs.
  • For plugin developers - the left hand side of the 'view issue' page can be customised via web panels. Hence, you can now insert your own custom panels anywhere below the operations bar on the 'view issue' page.
    (info) The web panel location for the left-hand side of the 'view issue' page is atl.jira.view.issue.left.context — refer to the View Issue Page Locations page of the Web Fragments guide in our Atlassian Developers documentation site for more information. Also see our plugin tutorial for an example of customising the right-hand side of the 'view issue' page (a feature which became available in JIRA 4.4).

^Top

 

JIRA Add-Ons (Plugins and Integrations)

JIRA 5.0 contains a great deal of new capabilities for developers who want to integrate with JIRA, including new integration features like remote issue links and activity streams, a new REST API (link) and a stable Java API.

JIRA Customers will already see the benefits of these new capabilities:

  • Over 100 integrations to JIRA 5.0 are available (at 5.0 release), so many of the plugins customers depend on are already JIRA 5.0 compatible.
  • JIRA's stable Java and new REST APIs allow Add-On developers to build integrations to JIRA which will be forwards compatible with future releases of JIRA 5.x, so upgrades become even easier for JIRA customers.
  • Many of these new integrations use the new activity streams and remote issue links features.

See the full list of JIRA 5.0 compatible integrations on the Atlassian Plugin Exchange.

^Top

Other enhancements and fixes

When you access your new or upgraded JIRA 5.0 installation, JIRA launches the What's New in JIRA ... dialog box, which provides brief overview of the new features available in that JIRA version.

(tick) This dialog box can be prevented from showing up whenever you access JIRA by selecting the Don't show again check box at the base of the dialog box. However, you can access this dialog box again by choosing the What's New item from your user name drop down menu.

For a list of more issues resolved in JIRA 5.0 so far, click here.

^Top

 

  • No labels

10 Comments

  1. Anonymous

    I'm confused about what is grouping the fields available to the Configure Fields button. Specifically Common and Agile in the screenshot applicable to feature #3 above.

    1. Hello there,

      The Agile set of fields will appear if you have the GreenHopper plugin installed into JIRA.

      Cheers,

      Giles.

  2. Anonymous

    Hi - is there a JIRA 101 available as a PDF (not the version in the docs as that's just HUGE!)? I'm looking for a way to understad the philosophy behind JIRA so that we set it up correctly and understand its capabilities correctly, specifically as we'd like to use Confluence too...

    Thanks

  3. Anonymous

    How to disable using dialog box for ticket edition. We have WYSIWYG editor which works better in main window but in this dialog box works buggy.

    Thank you.

    1. Anonymous

      Previous post is mine. I have found a workaround:

      1. New issues won't use overlay if opened in new window.
      2. If Green Hopper enabled. Open tab 'Agile' and click link 'Create Issue' and form will be opened in the same window without overlay.
  4. Anonymous

    For new feature number 4 (search history), what improved between 4.4.3 and 5.0? Comparing the JQL instructions between the documentation for Advanced Searching, I can't see what's new.

    1. Hello there,

      No changes were made to this feature between JIRA 4.4.3 and 5.0.

      We are re-iterating these features again on these release notes for the benefit of customers who upgrade JIRA less frequently and because the documentation for JIRA 4.4.x versions resides in a different space on this Confluence site to this documentation for JIRA 5.0.x versions. See How JIRA Documentation Updates are Published for more information.

      Cheers,

      Giles.

  5. Anonymous

    I like the changes (smile) Good work. Please include "time estimation" into the bulk change (wink)

  6. Anonymous

    The links to Screenshots on this page - when clicked on and closed do not refresh the page!

  7. Anonymous

    Setting Fix Versions of Sub-Tasks Question.

    When I create a sub-task, it inherits the Fix Version of the parent.

    But when I change the Fix Version of the parent ... the Fix Version of the sub-task is not updated.

    Other than adding a post function to transitions of the sub-task, "Set the value(s) of a field from the issue's parent" is there another way to keep the sub-task fix version in synch with its' parent?