Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

Go to main Jira page and nagivate to Apps → JQL Search Extensions

...

Extended search allows Search lets you to search through your Jira instance using JQL with the additional functions . There are many occasions when standard Jira search is too limiting. Follow the next section to learn how to use Extended search.

Usage

and keywords included with JQL Search Extensions for Jira. You can then save your query as a filter and use it anywhere you would use a Jira filter, for example, in advanced search, Jira dashboards, or to set the scope for features in third-party apps, including JSU, JMWE, Power Scripts, and BigPicture from Appfire. See App integrations to learn more

On this page:

Table of Contents
minLevel2
maxLevel3
outlinefalse
styledefault
typelist
printabletrue

How to use Extended Search

  1. In the top bar in Jira, select Apps>JQL Search Extensions. The Extended Search page displays.

  2. In the query input field, type a JQL query and

...

  1. click Searchor

...

  1. press Enteron your keypad.
    You can use additional functions provided by JQL Search Extensions. For example, to find all issues with a summary starting with “Hello”, type issue in wildcardMatch(

...

  1. "summary", "Hello*").

Tip

Want some help with queries or looking for inspiration? Try the in-app cheat sheet. Open the cheat sheet on the right side of the Extended Search page to see the full list of keywords and functions with examples.

...

Save the query as a filter

You can save your Extended JQL Search query as a Jira filter. After you perform your search, clickSave the query as a filterbutton actives after you perform a search.Read more about Extended search . See Extended Search filters to learn more about using and managing your saved filters.

JQL Functions

Extended search functions are invoked just like standard JQL functions. They are autocompleted after you start typing issue in…

ExactTextMatch

Matches issues that contain the text in the summary or description. Takes a case-sensitive text as an argument.

Example:
issue in exactTextMatch("text")

ExactTextMatchCaseInsensitive

Similar to exactTextMatch but is case insensitive.

Example:
issue in exactTextMatchCaseInsensitive("tExT") matches issues with TEXT, Text, tEXT etc.

WildcardMatch

Matches issues with a field containing a specified text (case-sensitive). You can use the asterisk (*) to match any text.

Examples:
issue in wildcardMatch("summary", "Hello*")
issue in wildcardMatch("fixVersion", "12.0*")
issue in wildcardMatch("labels", "*Marketing*")
issue in wildcardMatch("component", "Business*")
issue in wildcardMatch("category", "MyOrg*")

The star symbol can be placed anywhere in the text – you can even place more than one.

Regex

Use the full power of regular expressions to match field values. Regular expressions are strict and case sensitive.

Examples:

issue in regex("summary", "^Hello.*") matches issues with summaries starting with
issue in regex("fixVersion", "12.[0-5]") matches issues with versions from 12.0 to 12.5
issue in regex("labels", "Marketing$")matches issues with labels that end with Marketing
issue in regex("component", "Business.*")
issue in regex("category", "MyOrg.*")

EpicsOfChildrenInQuery

For a given JQL subquery it finds the epics of the resulting issues.

Examples:

issue in epicsOfChildrenInQuery("'Team Name'='My great team'") and status='To Do' finds my team’s epics that are still in progress
issue in epicsOfChildrenInQuery("assignee=currentUser() AND updated>-1d") finds epics of my issues that where updated over the last day

ChildrenOfEpicsInQuery

For a given JQL subquery it finds the children of the resulting epics.

Examples:

issue in childrenOfEpicsInQuery("resolution is not empty") AND resolution is empty finds issues in progress that belong to an epic which has finished
issue in childrenOfEpicsInQuery("fixVersion='21.0.1' AND component=UI AND labels='review'") finds children of epics with particular version, component and label

LinkedIssuesOfQuery

For a given JQL subquery and an optional link type, it finds issues linked to resulting issues.

issue in linkedIssuesOfQuery("project=ACME", "is blocked by") finds issues that my project ACME is blocked by
issue in linkedIssuesOfQuery("project=ACME", "blocks") finds issues that project ACME blocks
issue in linkedIssuesOfQuery("type=Epic AND status='To Do'") finds issues that are linked in any way with epics that are in progress

ParentsOfSubtasksInQuery

For a given JQL subquery it finds parents of resulting subtasks

Examples:

issue in parentsOfSubtasksInQuery("status='To Do'") and status='Done' finds finished issues that have unfinished subtasks
issue in parentsOfSubtasksInQuery("assignee=currentUser()") finds parents of my subtasks

SubtasksOfParentsInQuery

For a given JQL subquery it finds subtasks of resulting parent issues

Examples:

issue in subtasksOfParentsInQuery("status='Done'") and status='To Do' finds subtasks that are in progress and have finished parents
issue in subtasksOfParentsInQuery("assignee=currentUser()") finds subtasks of my issues

ParentsOfIssuesInQuery

For a given JQL subquery it finds parents of resulting issues. It supports Advanced Roadmaps “Parent Link” and a standard Jira hierachy Epic → Story → Subtask.

Also have a look at ParentsOfIssuesInQueryRecursive.

Examples:

issue in parentsOfIssuesInQuery("project='ACME' and type=Epic") finds all parents of epics in project ACME. Parents of epics are usually called Initiative.
issue in parentsOfIssuesInQuery("assignee=currentUser()") finds parents of all of my tickets.

ParentsOfIssuesInQueryRecursive

For a given JQL subquery it finds issues in the hierarchy above the resulting issues up to an optional depth. It supports Advanced Roadmaps “Parent Link” and a standard Jira hierachy Epic → Story → Subtask.

Examples:

issue in parentsOfIssuesInQueryRecursive("project='ACME' and type=Epic") finds all parents of epics in project ACME, and parents of parents, and so on. Parents of epics are usually called Initiative.
issue in parentsOfIssuesInQuery("assignee=currentUser() and issueType in subtaskIssueTypes()", 2) finds parents of my subtasks and epics of the parents, skips anything above epics.

ChildrenOfIssuesInQuery

For a given JQL subquery it finds children of resulting issues. It supports Advanced Roadmaps “Parent Link” and a standard Jira hierachy Epic → Story → Subtask. Also have a look at ChildrenOfIssuesInQueryRecursive.

Examples:

issue in childrenOfIssuesInQuery("project='ACME' and type=Initiative") finds all epics in initiatives in project ACME.
issue in childrenOfIssuesInQuery("assignee=currentUser()") finds children of all of my tickets.

ChildrenOfIssuesInQueryRecursive

For a given JQL subquery it finds issues in the hierarchy below the resulting issues up to an optional depth. It supports Advanced Roadmaps “Parent Link” and a standard Jira hierachy Epic → Story → Subtask.

Examples:

issue in childrenOfIssuesInQueryRecursive("project='ACME' and type=Initiative") finds all epics, stories and subtasks in initiatives in project ACME.
issue in childrenOfIssuesInQueryRecursive("assignee=currentUser() and type=Initiative", 2) finds epics and stories of all of my epics and skips the subtasks.

Permissions and feature availability to users

...

Extended Search JQL functions and keywords

For our full list of functions and keywords, including examples, see JQL functions and keywords reference.

See our use cases to discover how other customers use JQL Search Extensions for precise searching and project insights.

Permissions and feature availability

The Extended Search page is available through the Jira global permission that controls the visibility of the Extended Search feature. By default, this permission is granted to all Jira users.