Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Quick search

The quick search is the fastest way to define search criteria. However, it is less precise than other search methods for complex queries (e.g. project = Jira AND status = Open AND priority = High).
It is most useful when your search criteria is not complex, for example, you know the project key and some key words for an issue.

To use the quick search: Enter your search criteria in the search box in the header bar of Jira and press Enter.
Tip: If you know the issue key or project key, enter it before other search terms, e.g. "JRA help link is broken".  

More detailed information can be found on the following Atlassian page: Quick searching 

Basic search

The basic search is more precise than the quick search, but easier to use than the advanced search.
It provides a user-friendly interface that lets you define complex queries, without needing to know how to use JQL (advanced searching).

To use the basic search: Navigate to Issues (in header) > Search for issues, then enter your search criteria.
Tip: If the advanced search is shown instead of the basic search, click Basic next to the  icon.


More detailed information can be found on the following Atlassian page: Basic Search 

Advanced search

The advanced search is the most powerful of the three search methods. You can specify criteria that cannot be defined in the other searches (e.g. ORDER BY clause).
However, you need to know how to construct structured queries using the Jira Query Language (JQL) to use this feature.

To use the advanced search: Navigate to Issues (in header) > Search for issues, then enter your search criteria.
 Tip: If the basic search is shown instead of the advanced search, click Advanced next to the  icon.

You can choose which details are shown about the results, by choosing the Columns that should be displayed.

Searching for flagged issues

The flag for an issue is stored in a custom checkbox field named "Flagged", which has only one value: Impediment.

This means that you can use this JQL query to find flagged issues: Flagged = Impediment


More detailed information can be found on the following Atlassian page Advanced search in Jira 

View file
nameatlassian_jql-cheat-sheet.pdf
height250

Filters

The Jira Issue search functionality is enhanced by the ability to save searches, called filters in Jira, for later use.
More detailed information how to work with filters can be found on the following Atlassian page: Saving your search as a filter

...

  1. Navigate to your board.
  2. Click Backlog. If the Versions panel is not showing, click VERSIONS on the left side of the board (aligned vertically) to open it.

    Add a new versionClick Create version (you will need to hover over the 'VERSIONS' panel to show this link), enter the version details, and create it.
    * The Start Date is used to give you a more accurate Version Report in cases where you might plan a version many weeks or even months in advance, but not actually commence work until closer to the release date.
    * The End Date is used to calculate the days remaining in a release on the Release Hub.
    Update a version's detailsFor the version name, click the arrow next to the name, then choose Edit name
    For other fields (e.g. Description), click the field to edit it.
    Add an issue to a versionDrag and drop the issue onto the version in the 'VERSIONS' panel.
    Remove an issue from a versionDrag and drop the issue onto Issues without versions in the 'VERSIONS' panel.
    Filter issues by versionClick the version in the 'VERSIONS' panel to show only issues in that version. Click All issues to remove the filter. Alternatively, click Clear all filters next to the column's name.


    Screenshot: viewing versions in the Backlog

...

  • Go to the Backlog of your Scrum project.

  • Click VERSIONS on the left side of the board (aligned vertically) to open it.

    Add a new versionClick Create version (you will need to hover over the 'VERSIONS' panel to show this link), enter the version details, and create it.
    * The Start Date is used to give you a more accurate Version Report in cases where you might plan a version many weeks or even months in advance, but not actually commence work until closer to the release date.
    * The End Date is used to calculate the days remaining in a release on the Release Hub.
    Update a version's detailsFor the version name, click the arrow next to the name, then choose Edit name
    For other fields (e.g. Description), click the field to edit it.
    Add an issue to a versionDrag and drop the issue onto the version in the 'VERSIONS' panel.
    Remove an issue from a versionDrag and drop the issue onto Issues without versions in the 'VERSIONS' panel.
    Filter issues by versionClick the version in the 'VERSIONS' panel to show only issues in that version. Click All issues to remove the filter. Alternatively, click Clear all filters next to the column's name.


    • The blue horizontal bar under the version's name (in the 'VERSIONS' panel) indicates progress towards completing the work estimated for the version. Note that this bar only represents progress on the estimated issues in a version.
    • You can use the JQL fixVersion  field to search for a version's issues — see Search for details.

...