Working with search results

Still need help?

The Atlassian Community is here for you.

Ask the community

On this page:


When you run a search, you may want to triage the entire list of issues, or you may be looking for just one. Either way, you can change the way issues look in search results and modify the issues that appear.

Change your view of search results

List view or Detail view

Click the change view button ( or ) to switch between List view and Detail view for your search results.

  • List view: Shows your search results as a list of issues. This view is easiest to scan and is best when you only need to know a few details about each issue.
  • Detail view: Shows your search results as a list of issues, with the right panel showing the details of the currently selected issue. This view is best when you need more information about the individual issues, or you want to quickly edit issues as you go (via inline edit for certain fields).
Change the sort order

Click the column name. If you click the same column name more than once, the sort order will switch between ascending and descending. Note:

  • You can't sort by the Images column or the subtask aggregate columns (all columns beginning with '∑').
  • If you sort the search results for an advanced search, an ORDER BY clause is added/updated to your JQL query to reflect the order of issues in your search results.
Columns - show/hide and move

You can create different column configurations for yourself and for specific filters. To switch between different column configurations, click Columns and select one of the following tabs:

  • My Defaults: This is your default column configuration for search results.
  • Filter: This is enabled if you are viewing the search results for a filter. It will override your default column configuration.
  • System (shows if you are a Jira administrator): This is the column configuration that applies to all users. It will be overridden by a user's default column configuration and filter-specific column configurations.

You can also modify any of these configurations. Make sure you have switched the desired configuration, then do the following:

  • Show/hide columns: Click Columns, choose the desired columns, then click Done.
  • Move a column: Click the column name and drag it to the desired position.

If you can't find a column, make sure that you haven't run into any of the following restrictions:

  • You can only see columns for issue fields that haven't been hidden and that you have permission to see.
  • It's possible to add any of the existing custom fields to the column list, as long as the fields are visible and you have the right permissions.
  • Some custom fields, even if selected, don't appear in the issue navigator for all issues. For example, project-specific custom fields will be shown only if the filter has been restricted to the relevant project. Issue type custom fields will only appear if the filter has been restricted to the relevant issue type.

Edit individual issues

You can action individual issues in your search results, directly from the issue navigator.

tip/resting Created with Sketch.

The list of issues will remain constant, even if you change an issue so that it doesn't meet the original search criteria. This is to give you a constant set of issues to work with when triaging issues.

View an issue

Click the key or summary of the issue.

  • If you're in list view, you will be redirected to the issue (leaving the search results page).
  • If you're in detail view, the issue details will display in a panel on the right.
Edit an issue

To edit an issue (update fields, transition it, or log time on it, for example):

  • If you're in list view, hover over the issue and click the ••• icon and select from the options.
  • If you're in detail view, select the issue and update it in the issue details panel on the right.
tip/resting Created with Sketch.

You can also select an issue and update it via keyboard shortcuts in either view. Use the j and k keys to select the previous/next issue in the issue navigator.




tip/resting Created with Sketch.

We're refreshing the Issues section of your projects. It has a new, cleaner look and includes the new Jira issue view to help you quickly find and update important issue details.

Note: Create issue and navigation with keyboard shortcuts aren't available in the new issue navigator just yet, but we hope to add them very soon. The in the sidebar is always there for when you need to create new issues.

Bulk edit issues

Bulk operations let you edit multiple issues at once. These actions include transitioning issues, deleting issues, moving issues, and watching or unwatching issues.

Select more (•••) > Bulk change all <N> issue(s) and follow the Bulk Operation wizard.

Share search results

Click the share icon () at the top-right of the screen to email a link to a search result or filter.

  • Recipients will receive an email with a link to the search and the content of the Note field (if specified). The subject of the email will state that you (using your username) shared the issue.
  • If you share a filter, rather than an unsaved search, recipients will receive a link to the filter. If the recipient doesn't have permission to view the filter, they will receive a link to the search results instead.

Display search results in Confluence

If your Jira site is connected to Confluence, use the Jira issues macro to display search results on a page.

tip/resting Created with Sketch.

Copy the link to your filter and paste it on a Confluence page, and it'll automatically add the Jira issues macro.

Use search results as a dashboard gadget

To create a dashboard gadget from your search results:

  1. Select Export ( ) > Create dashboard gadget.
  2. Choose the type of gadget you want to use to display the results.
  3. Select Save to Dashboard.

The chart will be added to your dashboard. For more information on what each chart shows, see Reporting.

Export search results

Word

To export to Word:

  1. Select Export ( ).
  2. Select Export Word.

The export will include the Description, Comments, and all other issue data, not just the issue fields that are currently configured in your Issue Navigator. Note, large exports (e.g. hundreds of issues) are not recommended.

XML

To export to XML:

  1. Select Export ( ).
  2. Select Export XML.

You can use the URL of the XML view in a Confluence Jira issues macro. However, you can also use the JQL or the URL of the issue search, which are easier to get.

To restrict which issue fields are returned in the XML export, specify the field parameter in your URL. For example, to include only the Issue key and Summary, add &field=key&field=summary to the URL. If the field parameter is not specified, the XML output will include all the issue fields. Otherwise, if one or more field parameters are specified, the XML output will contain only the Issue key plus your chosen field(s). See the "List of fields for field parameter" below.


List of fields for field parameter (XML exports)

Value

Sample XML output

Notes

title

<title>[TEST-4] This is a test</title>


link

<link>https://extranet.atlassian.com:443/jira/browse/TEST-4</link>

This is a 'permalink' to the issue. For links between issues, see * issuelinks * (below).

project (or pid)

<project id="10330" key="TST">Test</project>


description

<description>This is a detailed description of the issue.<description>


environment

<environment>Sydney network<environment>


key

<key id="22574">TEST-4</key>


summary

<summary>This is a test<summary>


type (or issuetype)

<type id="3" iconUrl="https://extranet.atlassian.com:443/jira/images/icons/task.gif">Task</type>


parent

<parent id="22620">TEST-5</parent>

Only relevant if the issue is a sub-task.

priority

<priority id="4" iconUrl="https://extranet.atlassian.com:443/jira/images/icons/priority_minor.gif">Minor<priority>


status

<status id="5" iconUrl="https://extranet.atlassian.com:443/jira/images/icons/status_resolved.gif">Resolved</status>


resolution

<resolution id="1">Fixed</resolution>


labels

<labels>
<label>focus</label>
<labels>


assignee

<assignee username="jsmith">John Smith</assignee>


reporter

<assignee username="jsmith">John Smith</assignee>


security

<security id="10021">Private</security>

Only relevant if a security level has been applied to the issue.

created

<created>Mon, 1 Sep 2008 17:30:03 -0500 (CDT)>/created>


updated

<updated>Mon, 1 Sep 2008 17:30:03 -0500 (CDT)>/updated>


resolved (or resolutiondate)

<resolved>Mon, 1 Sep 2008 17:30:03 -0500 (CDT)>/resolved>


due (or duedate)

<due>Mon, 1 Sep 2008 17:30:03 -0500 (CDT)>/due>


version (or versions)

<version>2.4.7</version>


fixfor (or fixVersions)

<fixVersion>2.6</fixVersion>


component (or components)

<component>Documentation</component>


votes

<votes>1</votes>


comments (or comment)

<comments>
    <comment id="39270" author="jsmith" created="Tue, 24 Feb 2009 16:45:02 -0600 (CST)">this looks familiar</comment>
    <comment id="39273" author="jbrown" created="Tue, 24 Feb 2009 16:48:16 -0600 (CST)">to me too</comment>
</comments>


attachments (or attachment)

<attachments>
   <attachment id="30318" name="Issue Navigator - Atlassian JIRA-2.png" size="16161" author="yoz" created="Mon, 9 Feb 2009 13:32:58 -0600 (CST)"/>
   <attachment id="30323" name="Windows XP (with Firefox 3.0).jpg" size="5802" author="vbharara" created="Tue, 10 Feb 2009 00:30:11 -0600 (CST)"/>
</attachments>

Only available if your administrator has enabled attachments.

timeoriginalestimate

<timeoriginalestimate seconds="600">10 minutes</timeoriginalestimate>

Only available if your administrator has time tracking enabled.

timeestimate

<timeestimate seconds="300">5 minutes</timeestimate>

Only available if your administrator has time tracking enabled.

timespent

<timespent seconds="300">5 minutes</timespent>

Only available if your administrator has time tracking enabled.

aggregatetimeoriginalestimate

<aggregatetimeoriginalestimate seconds="36000">10 hours</aggregatetimeoriginalestimate>

Aggregate time for the issue plus all of its sub-tasks. Only available if your administrator has time tracking enabled.

aggregatetimeestimate

<aggregatetimeremainingestimate seconds="18000">5 hours</aggregatetimeremainingestimate>

Aggregate time for the issue plus all of its sub-tasks. Only available if your administrator has time tracking enabled.

aggregatetimespent

<aggregatetimespent seconds="18000">5 hours</aggregatetimespent>

Aggregate time for the issue plus all of its sub-tasks. Only available if your administrator has time tracking enabled.

timetracking

<timeoriginalestimate seconds="600">10 minutes</timeoriginalestimate>
<timeestimate seconds="300">5 minutes</timeestimate>
<timespent seconds="300">5 minutes</timespent>
<aggregatetimeoriginalestimate seconds="36000">10 hours</aggregatetimeoriginalestimate>
<aggregatetimeremainingestimate seconds="18000">5 hours</aggregatetimeremainingestimate>
<aggregatetimespent seconds="18000">5 hours</aggregatetimespent>

This is a convenient shorthand way of specifying all of the above six time tracking fields. Only available if your administrator has time tracking enabled.

issuelinks

<issuelinks>
    <issuelinktype id="10020">
        <name>Duplicate</name>
        <inwardlinks description="is duplicated by">
            <issuelink>
                <issuekey id="22477">INTSYS-1009</issuekey>
            </issuelink>
        </inwardlinks>
    </issuelinktype>
</issuelinks>


subtasks (or subtask)

<subtasks>
    <subtask id="22623">TEST-8</subtask>
</subtasks>


customfield_xxxxx

<customfields>
    <customfield id="customfield_10112" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
        <customfieldname>Department</customfieldname>
        <customfieldvalues>
            <customfieldvalue>Adminstration</customfieldvalue>
        </customfieldvalues>
    </customfield>
</customfields>

"xxxxx" is the id of a given custom field e.g. this output is the result of specifying &field=customfield_10112

allcustom

<customfields>
    <customfield id="customfield_10112" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
        <customfieldname>Department</customfieldname>
        <customfieldvalues>
            <customfieldvalue>Adminstration</customfieldvalue>
        </customfieldvalues>
    </customfield>
    <customfield id="customfield_10111" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
        <customfieldname>Expenditure Type</customfieldname>
        <customfieldvalues>
            <customfieldvalue>Operating</customfieldvalue>
        </customfieldvalues>
    </customfield>
</customfields>

Subscribe to search results

A subscription provides you with a periodic notification for all issues returned by a search. To be notified when a particular issue changes, choose  to watch the issue.

Email

Your search must be saved as a filter if you want to create an email subscription for it. You can create a subscription of any frequency for yourself and/or other users. Only the first 200 results of a filter are sent.

  1. Run the filter that you want to subscribe to, then click Details (next to the filter name).
  2. Fill in the Filter subscription form and click Subscribe.

More information:

  • If you choose Advanced for your Schedule, see this page for help on constructing Cron expressions.
  • To specify a group as a recipient:
    • You must have the Manage group filter subscriptions global permission.
    • Be aware that the emailed filter results will be specific to each recipient. For example, if the filter uses the currentUser() function, the search results will be evaluated with the recipient as the current user. This doesn't apply to distribution lists (group email aliases).
    • Be careful about sharing a subscription with a group with many members. It can take a long time to generate the emails to be sent, since the search needs to be executed for each user (as per the previous point).
  • Subscription emails should be sent as HTML rather than plain text, as the email can appear broken in plain text. See Manage your Jira personal settings for instructions on updating your own email preference to HTML. If you're a Jira admin, take a look at Configuring the user default settings to find out how to set default email settings.
RSS

To subscribe to a filter's RSS feed:

  1. Select Export ( ).
  2. Select either RSS or RSS (with comments). The URL of the page that shows can be used in your feed reader.

Tips:

  • You can change the number of issues returned by changing the value of the tempMax parameter in the URL.
  • If you only want to receive current comments in an RSS feed, use the Date Updated field when doing a search. For example, to only receive comments created in the last week, add the Date Updated field and set it to updated within the last 1 week.
  • You may need to log in to Jira to view restricted data in your feed. If so, you can add os_authType=basic to the feed URL (e.g. http://mycompany.com/anypage?os_authType=basic) to show a login dialog when viewing the feed.
Last modified on Jul 18, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.