Documentation for JIRA 4.1. Documentation for other versions of JIRA is available too.

Skip to end of metadata
Go to start of metadata

The Issue Navigator displays the search results from an issue filter, a Quick Search or an Advanced Search, e.g:

The Issue Navigator provides convenient ways to perform many of JIRA's most useful functions. You can:

  • Use the 'Actions' icon menu for a particular issue to quickly:
    • Resolve issue — Set the issue's Status to 'Resolved' and select the appropriate Resolution.
    • Close issue — Set a resolved issue's Status to 'Closed'.
    • Reopen issue — Set a resolved or closed issue's Status to 'Reopened'.
    • Assign this issue — Select an asignee for the issue.
    • Assign this issue to me — Assign the issue to yourself.
    • Attach file to this issue — Select a file, upload it and attach it to the issue.
    • Clone this issue — Create a new issue which is a copy of the issue.
    • Comment on this issue — Add a comment to the issue.
    • Delete this issue — Permanently remove the issue.
    • Edit this issue — Edit the issue's details (Summary, Description, etc).
    • Link this issue — Create a link between the issue and another issue.
    • Move this issueMove the issue to a different project.
    • Create sub-task for this issue — Create a new issue which is a sub-task of the issue.
    • Convert sub-task to issue — If the issue is a sub-task, convert it to a standalone issue.
    • Start watching this issue — Become a watcher of the issue.
    • Log work for this issue — Record the work done and time spent on the issue.

      Note that the options in the Actions menu will only be available if you have the necessary permissions, and that options which change an issue's Status (Resolve issue, Close issue, Reopen issue) may differ from this list, depending on your organisation's workflow.

  • Use the 'Views' menu to view/export your search results in various formats:
    • Printable — All search results on one page, with one row of data per issue. Includes the issue fields that are currently configured in your Issue Navigator.
    • Full Content — All search results on one page. Includes Description, Comments and all other issue data, not just the issue fields that are currently configured in your Issue Navigator.
    • XML — An XML view of issue data, suitable for use with the Confluence JIRA Issues Macro. (Also suitable for use as an RSS 0.9.2 feed). For details, see 'Displaying Search Results in XML'.
    • RSS (Issues) — An RSS 2.0 feed of issue data, suitable for displaying in an RSS reader. For details, see 'Receiving Search Results via RSS'.
    • RSS (Comments) — An RSS 2.0 feed of comments on the issues, suitable for displaying in an RSS reader. For details, see 'Receiving Search Results via RSS'.
    • Word — An MS Word document. Includes Description, Comments and all other issue data, not just the issue fields that are currently configured in your Issue Navigator. Can be saved and/or edited. For details, see 'Exporting Search Results to Microsoft Word'.
    • Excel (All fields) — An MS Excel spreadsheet. Includes Description and all other issue data (excluding comments). Can be saved, or edited to produce graphs and charts; also useful for basic reporting and statistics. For details, see 'Exporting Search Results to Microsoft Excel'.
    • Excel (Current fields) — An MS Excel spreadsheet containing the issue fields that are currently configured in your Issue Navigator. Can be saved, or edited to produce graphs and charts; also useful for basic reporting and statistics. For details, see 'Exporting Search Results to Microsoft Excel'.
    • Charts — A graphical summary of the search results, which can be saved as a dashboard portlet. For details, see 'Displaying Search Results as a Chart'.
  • Use the 'Tools' menu to:
  • Click the 'permalink' icon to create a permanent URL link to your search results.

The Issue Navigator only displays one set of search results at any one time, even if you have multiple browser windows open. However, you can easily save your searches (see 'issue filters'), then display them as needed.

Re-ordering the search results

When viewing search results in the Issue Navigator, you can re-order the issues by clicking on the column header*. For example, if you click the 'Reporter' column header, the Issue Navigator will re-display the issues in ascending order of reporter's name. If you click the 'Reporter' column header a second time, the Issue Navigator will re-display the issues in descending order of reporter's name.

  • With some exceptions, e.g. the 'Images' column and the sub-task aggregate columns (i.e. all columns beginning with '∑') are non-orderable.

To choose different fields to display in your Issue Navigator, see Customising your Issue Navigator.

Viewing individual issues

When an issue from a search result set is selected and displayed, a mini-navigator is shown at the right of the issue's title bar:

This mini-navigator indicates the current issue's position within the result set. It also provides linked arrow icons to the previous and next issues in the result set (as shown in the image above), along with a 'Return to search' link that leads you back to the search results. You can also navigate through the search results by using the shortcut keys: 'p' (previous) and 'n' (next).

Accessing protected data

When accessing data generated from JIRA, you may find that access to some resources requires user authentication (i.e. requires you to login). There are three options for this:
  1. To enable access to data without logging in, your JIRA administrator may specify the 'Browse' permission for Anyone.
  2. You can provide the parameters os_username and os_password in the request URL (e.g. http://jira.atlassian.com/browse/TST-1?os_username=tester&os_password=tstpassword). The problem with this method is that it transmits your username and password across the wire in clear text, which may not be an option for some users.
  3. You can provide the request parameter os_authType=basic (e.g. http://mycompany.com/anypage?os_authType=basic). This will force the server to issue a challenge for user credentials (i.e. a login prompt) via the basic http authentication protocol. If you are running over SSL, you still need to specify the os_authType=basic parameter if you require the user to authenticate.