remote-issue-links.png

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 via application links.
  • Add a reciprocal issue link from your JIRA issue to an issue another JIRA site.
• Search for a Confluence page from a JIRA issue and add an issue link to that page via application links.
• 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.

share-issue.png

Screenshot: Sharing an issue with other users

mentions.png

Screenshot: Mentioning a user in an issue comment

Want to let others know about a JIRA issue or a list of search results quickly? Simply visit a JIRA issue or a list of issues on the issue navigator and then do either of the following:

• Click the new 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 page with. Add an optional note and then click Share.

JIRA users specified in the User name or email field will receive details of the issue or a link to a list of issues in an email message (sent to the addresses registered with their JIRA user accounts). The message's subject line will indicate that the person who used this feature 'shared' the issue(s) with them.

• In an issue comment or the issue's description field, type the @ symbol and begin typing the name or username of a JIRA user. Select the appropriate user from the dropdown. You can do this with multiple users and after submitting the form, those users will be notified that you mentioned them in the comment or the issue's description field.

Users will receive details of the issue in an email message (sent to the addresses registered with their JIRA user accounts). The message's subject line will indicate that the person who used this feature 'mentioned' them on that issue.

Please Note:

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

create-issue.png

JIRA 5.0 provides a rapid and customisable dialog box for creating and editing JIRA issues and sub-tasks. Unlike the old Create/Edit Issue forms, these dialog boxes do not require a page reload.

By default, the Create/Edit Issue dialog boxes show all available fields, which you can quickly remove or re-add. JIRA remembers your last set of field choices, giving you a personally customised dialog box that presents you with your most commonly edited fields whenever you create or edit an issue.

jql-changed-report.png

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

activity-stream-atlassian-apps.png

Screenshot: Activity stream gadget showing activity
from other Atlassian applications

activity-stream.jpg

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

We are expanding 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.

shared-dashboards.png

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.

edit-attachment-settings-dialog-box.png

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

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.

For example, the form for editing attachment settings is now a dialog box, which is accessed by clicking 'Edit Settings' on the 'Attachments' page of JIRA's Administration area.

mail-handler-wizard.png

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

You no longer have to configure a JIRA service and enter in a complex string of Handler parameters for your email handler. Instead you configure your email 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' tab has been separated into two tabs — one for 'Outgoing Mail' (SMTP) and another for 'Incoming Mail' (POP/IMAP) configuration. The configuration options for mail handlers in the 'Services' tab has been incorporated into the 'Incoming Mail' tab.

remote-issue-copying-action.jpg

This new JIRA 5.0-compatible feature currently under development as a plugin, allows you to copy issues from one JIRA site to another.

After establishing an Application Link between your JIRA site and another and one or more Project Links across these sites, a new 'Remote Copy' action will become available when viewing an issue belonging to a project involved in this project link.

Using JIRA to JIRA issue copy

After clicking the 'Remote Copy' menu item, the Remote Copy 'wizard' will prompt you to choose a remote JIRA project to copy the issue to and will then automatically map fields between your local and remote JIRA projects.

Most system fields and some custom fields are supported. For a detail list of supported fields, see our Issue Field copy rules documentation.

When copying an issue, you can define a bidirectional remote 'issue link' between the issues. If the remote site is on a version of JIRA that does not support remote 'issue links' (prior to 5.0), you can create a single remote 'issue link' from the local issue to the remote issue and a comment will be added to the remote issue with a link to the local issue it was copied from.