Advanced searching - functions reference
approver()
Only applicable if Jira Service Management is installed and licensed.
Search for issues that require or required approval by one or more of the listed users. This uses an OR
operator, and you must specify the usernames.
Syntax | approver(user,user) |
---|---|
Supported fields | Custom fields of type Approval |
Supported operators | = |
Unsupported operators | |
Examples |
|
breached()
Only applicable if Jira Service Management is installed and licensed.
Returns issues that whose most recent has missed its goal.
Syntax | breached() |
---|---|
Supported fields | |
Supported operators | = , != |
Unsupported operators | |
Examples |
|
cascadeOption()
Search for issues that match the selected values of a "cascading select" custom field.
The parentOption
parameter matches against the first tier of options in the cascading select field. The childOption
parameter matches against the second tier of options in the cascading select field, and is optional.
The keyword "none"
can be used to search for issues where either or both of the options have no value.
Syntax | cascadeOption(parentOption) cascadeOption(parentOption,childOption) |
---|---|
Supported fields | Custom fields of type "Cascading Select" |
Supported operators | IN , NOT IN |
Unsupported operators | = , != , ~ , !~ , > , >= , < , <= , |
Examples |
|
closedSprints()
Search for issues that are assigned to a completed Sprint.
It's possible for an issue to belong to both a completed Sprint(s) and an incomplete Sprint(s). See also openSprints().
Syntax | closedSprints() |
---|---|
Supported fields | Sprint |
Supported operators | IN , NOT IN |
Unsupported operators | = , != , ~ , !~ , > , >= , < , <= |
Examples |
|
completed()
Only applicable if Jira Service Management is installed and licensed.
Returns issues that have an that has completed at least one cycle.
Syntax | completed() |
---|---|
Supported fields | |
Supported operators | = , != |
Unsupported operators | = , |
Examples |
|
componentsLeadByUser()
Find issues in components that are led by a specific user. You can optionally specify a user, or if the user is omitted, the current user (i.e. you) will be used.
If you are not logged in to Jira, a user must be specified.
Syntax | componentsLeadByUser() componentsLeadByUser(username) |
---|---|
Supported fields | Component |
Supported operators | IN , NOT IN |
Unsupported operators | = , != , ~ , !~ , > , >= , < , <= , |
Examples |
|
currentLogin()
Perform searches based on the time at which the current user's session began. See also lastLogin().
Syntax | currentLogin() |
---|---|
Supported fields | Created, Due, Resolved, Updated, custom fields of type Date/Time |
Supported operators | = , != ,
|
Unsupported operators | ~ , !~ , |
Examples |
|
currentUser()
Perform searches based on the currently logged-in user.
This function can only be used by logged-in users. If you are creating a saved filter that you expect to be used by anonymous users, don't use this function.
Syntax | currentUser() |
---|---|
Supported fields | Assignee, Reporter, Voter, Watcher, custom fields of type User |
Supported operators | = , != |
Unsupported operators | ~ , !~ , |
Examples |
|
earliestUnreleasedVersion()
Perform searches based on the earliest unreleased version (i.e. next version that is due to be released) of a specified project. See also unreleasedVersions.
Consider that the "earliest" is determined by the ordering assigned to the versions, not by actual Version Due Dates.
Syntax | earliestUnreleasedVersion(project) |
---|---|
Supported fields | AffectedVersion, FixVersion, custom fields of type Version |
Supported operators |
|
Unsupported operators | IN , NOT IN |
Examples |
|
elapsed()
Only applicable if Jira Service Management is installed and licensed.
Returns issues whose clock is at a certain point relative to a cycle's start event.
Syntax | elapsed() |
---|---|
Supported fields | |
Supported operators | = , != , |
Unsupported operators | |
Examples |
|
endOfDay()
Perform searches based on the end of the current day. See also endOfWeek(), endOfMonth(), and endOfYear(), startOfDay(), startOfWeek(), startOfMonth(), and startOfYear().
Syntax | endOfDay() endOfDay("inc") where |
---|---|
Supported fields | Created, Due, Resolved, Updated, custom fields of type Date/Time |
Supported operators |
|
Unsupported operators | ~ , !~ , |
Examples |
|
endOfMonth()
Perform searches based on the end of the current month. See also endOfDay(), endOfWeek(), endOfYear(), startOfDay(), startOfWeek(), startOfMonth(), and startOfYear().
Syntax | endOfMonth() endOfMonth("inc") where |
---|---|
Supported fields | Created, Due, Resolved, Updated, custom fields of type Date/Time |
Supported operators |
|
Unsupported operators | ~ , !~ , |
Examples |
|
endOfWeek()
Perform searches based on the end of the current week. See also endOfDay(), endOfMonth(), endOfYear(), startOfDay(), startOfWeek(), startOfMonth(), and startOfYear.
For the endOfWeek()
function, the result depends upon your locale. For example, in Europe, the first day of the week is generally considered to be Monday, while in the USA, it is considered to be Sunday.
Syntax | endOfWeek() endOfWeek("inc") where |
---|---|
Supported fields | Created, Due, Resolved, Updated, custom fields of type Date/Time |
Supported operators |
|
Unsupported operators | ~ , !~ , |
Examples |
|
endOfYear()
Perform searches based on the end of the current year. See also startOfDay(), startOfWeek(), startOfMonth(), endOfDay(), endOfWeek(), endOfMonth(), and endOfYear().
Syntax | endOfYear() endOfYear("inc") where |
---|---|
Supported fields | Created, Due, Resolved, Updated, custom fields of type Date/Time |
Supported operators |
|
Unsupported operators | ~ , !~ , |
Examples |
|
everbreached()
Only applicable if Jira Service Management is installed and licensed.
Returns issues that have missed one of their goals.
Syntax | elapsed() |
---|---|
Supported fields | |
Supported operators | = , != |
Unsupported operators | |
Examples |
|
futureSprints()
Search for issues that are assigned to a sprint that hasn't been started yet.
It is possible for an issue to belong to both completed and incomplete sprints.
Syntax | futureSprints() |
---|---|
Supported fields | Sprint |
Supported operators | IN , NOT IN |
Unsupported operators | = , != , ~ , !~ , > , >= , < , <= |
Examples |
|
issueHistory()
Find issues that you have recently viewed, i.e. issues that are in the Recent Issues section of the Issues dropdown menu.
Note that:
issueHistory()
returns up to 60 issues, whereas the Recent Issues drop-down returns only 5.- if you are not logged in to Jira, only issues from your current browser session will be included.
issues older than 90 days are deleted daily by the scheduled job.
Syntax | issueHistory() |
---|---|
Supported fields | Issue |
Supported operators |
|
Unsupported operators |
, |
Examples |
|
issuesWithRemoteLinksByGlobalId()
Perform searches based on issues that are associated with remote links that have any of the specified global IDs.
This function accepts 1 to 100 globalIds. Specifying 0 or more than 100 globalIds will result in errors.
Syntax | issuesWithRemoteLinksByGlobalId() |
---|---|
Supported fields | Issue |
Supported operators |
|
Unsupported operators |
, |
Examples |
|
lastLogin()
Perform searches based on the time at which the current user's previous session began. See also currentLogin().
Syntax | lastLogin() |
---|---|
Supported fields | Created. Due, Resolved, Updated, custom fields of type Date/Time |
Supported operators |
|
Unsupported operators |
|
Examples |
|
latestReleasedVersion()
Perform searches based on the latest released version (i.e. the most recent version that has been released) of a specified project. See also releasedVersions().
Consider that the "latest" is determined by the ordering assigned to the versions, not by actual Version Due Dates.
Syntax | latestReleasedVersion(project) |
---|---|
Supported fields | AffectedVersion, FixVersion, custom fields of type Version |
Supported operators |
|
Unsupported operators |
|
Examples |
|
linkedIssues()
Perform searches based on issues that are linked to a specified issue. You can optionally restrict the search to links of a particular type.
Note that LinkType is case-sensitive.
Syntax | linkedIssues(issueKey) linkedIssues(issueKey,linkType) |
---|---|
Supported fields | Issue |
Supported operators |
|
Unsupported operators |
, |
Examples |
|
membersOf()
Perform searches based on the members of a particular group.
Syntax | membersOf(Group) |
---|---|
Supported fields | Assignee, Reporter, Voter, Watcher, custom fields of type User |
Supported operators |
|
Unsupported operators |
, |
Examples |
|
myApproval()
Only applicable if Jira Service Management is installed and licensed.
Search for issues that require approval or have required approval by the current user.
Syntax | myApproval() |
---|---|
Supported fields | Custom fields of type Approval |
Supported operators | = |
Unsupported operators | ~ > , >= , < , <=
|
Examples |
|
myPending()
Only applicable if Jira Service Management is installed and licensed.
Search for issues that require approval by the current user.
Syntax | myPending() |
---|---|
Supported fields | Custom fields of type Approval |
Supported operators | = |
Unsupported operators | ~ > , >= , < , <=
|
Examples |
|
now()
Perform searches based on the current time.
Syntax | now() |
---|---|
Supported fields | Created. Due, Resolved, Updated, custom fields of type Date/Time |
Supported operators |
|
Unsupported operators |
|
Examples |
|
openSprints()
Search for issues that are assigned to a Sprint that has not yet been completed.
It's possible for an issue to belong to both a completed Sprint(s) and an incomplete Sprint(s). See also closedSprints().
Syntax | openSprints() |
---|---|
Supported fields | Sprint |
Supported operators | IN , NOT IN |
Unsupported operators | = , != , ~ , !~ , > , >= , < , <= |
Examples |
|
outdated()
Only applicable if Jira Service Management (Server) is installed and licensed.
Returns issues whose SLAs are out of date because someone has changed the SLA in the settings. After the site reindexes and recalculates the SLAs, the function shouldn't return any issues. Use this function if a reindex is taking a long time or if you've deferred the reindex because you're making a lot of changes.
Syntax | outdated() |
---|---|
Supported fields | |
Supported operators | = , != |
Unsupported operators | ~ , !~ , > , >= , < , <= , IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED |
Examples |
|
paused()
Only applicable if Jira Service Management is installed and licensed.
Returns issues that have an SLA that is paused due to a condition.
To find issues that are paused because they are outside calendar hours, use withincalendarhours().
Syntax | paused() |
---|---|
Supported fields | |
Supported operators | = , != |
Unsupported operators | |
Examples |
|
pending()
Only applicable if Jira Service Management is installed and licensed.
Search for issues that require approval.
Syntax | pending() |
---|---|
Supported fields | Custom fields of type Approval |
Supported operators | = |
Unsupported operators | ~ > , >= , < , <=
|
Examples |
|
pendingBy()
Only applicable if Jira Service Management is installed and licensed.
Search for issues that require approval by one or more of the listed users. This uses an OR
operator, and you must specify the usernames.
Syntax | pendingBy(user1,user2) |
---|---|
Supported fields | Custom fields of type Approval |
Supported operators | = |
Unsupported operators | ~ > , >= , < , <=
|
Examples |
|
projectsLeadByUser()
Find issues in projects that are led by a specific user. You can optionally specify a user, or if the user is omitted, the current user will be used.
If you are not logged in to Jira, a user must be specified.
Syntax | projectsLeadByUser() projectsLeadByUser(username) |
---|---|
Supported fields | Project |
Supported operators | IN , NOT IN |
Unsupported operators | = , != , ~ , !~ , > , >= , < , <= |
Examples |
|
projectsWhereUserHasPermission()
Find issues in projects where you have a specific permission. Note, this function operates at the project level. This means that if a permission (e.g. "Edit Issues") is granted to the reporter of issues in a project, then you may see some issues returned where you are not the reporter, and therefore don't have the permission specified. Also note, this function is only available if you are logged in to Jira.
Syntax | projectsWhereUserHasPermission(permission) For the |
---|---|
Supported fields | Project |
Supported operators | IN , NOT IN |
Unsupported operators | = , != , ~ , !~ , > , >= , < , <= |
Examples |
|
projectsWhereUserHasRole()
Find issues in projects where you have a specific role. Note, this function is only available if you are logged in to Jira.
Syntax | projectsWhereUserHasRole(rolename) |
---|---|
Supported fields | Project |
Supported operators | IN , NOT IN |
Unsupported operators | = , != , ~ , !~ , > , >= , < , <= |
Examples |
|
releasedVersions()
Perform searches based on the released versions (i.e. versions that your Jira administrator has released) of a specified project. You can also search on the released versions of all projects, by omitting the project parameter. See also latestReleasedVersion().
Syntax | releasedVersions() releasedVersions(project) |
---|---|
Supported fields | AffectedVersion, FixVersion, custom fields of type Version |
Supported operators | IN , NOT IN |
Unsupported operators |
|
Examples |
|
remaining()
Only applicable if Jira Service Management is installed and licensed.
Returns issues whose clock is at a certain point relative to the goal.
Syntax | remaining() |
---|---|
Supported fields | |
Supported operators | = , !=, |
Unsupported operators | |
Examples |
|
running()
Only applicable if Jira Service Management is installed and licensed.
Returns issues that have an SLA that is running, regardless of the calendar.
To find issues that are running based on calendar hours, use withincalendarhours().
Syntax | running() |
---|---|
Supported fields | |
Supported operators | = , != |
Unsupported operators | |
Examples |
|
standardIssueTypes()
Perform searches based on "standard" Issue Types, that is, search for issues that are not sub-tasks. See also subtaskIssueTypes().
Syntax | standardIssueTypes() |
---|---|
Supported fields | Type |
Supported operators | IN , NOT IN |
Unsupported operators |
|
Examples |
|
startOfDay()
Perform searches based on the start of the current day. See also startOfWeek(), startOfMonth(), startOfYear(), endOfDay(), endOfWeek(), endOfMonth(), and endOfYear().
Syntax | startOfDay() startOfDay("inc") where |
---|---|
Supported fields | Created, Due, Resolved, Updated, custom fields of type Date/Time |
Supported operators |
|
Unsupported operators | ~ , !~ , |
Examples |
|
startOfMonth()
Perform searches based on the start of the current month. See also startOfDay(), startOfWeek(), startOfYear(), endOfDay(), endOfWeek(), endOfMonth(), and endOfYear().
Syntax | startOfMonth() startOfMonth("inc") where |
---|---|
Supported fields | Created, Due, Resolved, Updated, custom fields of type Date/Time |
Supported operators |
|
Unsupported operators | ~ , !~ , |
Examples |
|
startOfWeek()
Perform searches based on the start of the current week. See also startOfDay(), startOfMonth(), startOfYear(), endOfDay(), endOfWeek(), endOfMonth(), and endOfYear().
For the startOfWeek() function, the result depends upon your locale. For example, in Europe, the first day of the week is generally considered to be Monday, while in the USA, it is considered to be Sunday.
Syntax | startOfWeek() startOfWeek("inc") where |
---|---|
Supported fields | Created, Due, Resolved, Updated, custom fields of type Date/Time |
Supported operators |
|
Unsupported operators | ~ , !~ , |
Examples |
|
startOfYear()
Perform searches based on the start of the current year. See also startOfDay(), startOfWeek(), startOfMonth(), endOfDay(), endOfWeek(), endOfMonth(), and endOfYear.
Syntax | startOfYear() startOfYear("inc") where |
---|---|
Supported fields | Created, Due, Resolved, Updated, custom fields of type Date/Time |
Supported operators |
|
Unsupported operators | ~ , !~ , |
Examples |
|
subtaskIssueTypes()
Perform searches based on issues that are sub-tasks. See also standardIssueTypes().
Syntax | subtaskIssueTypes() |
---|---|
Supported fields | Type |
Supported operators | IN , NOT IN |
Unsupported operators |
|
Examples |
|
unreleasedVersions()
Perform searches based on the unreleased versions (i.e. versions that your Jira administrator has not yet released) of a specified project. You can also search on the unreleased versions of all projects, by omitting the project
parameter. See also earliestUnreleasedVersion().
Syntax | unreleasedVersions() unreleasedVersions(project) |
---|---|
Supported fields | AffectedVersion, FixVersion, custom fields of type Version |
Supported operators |
|
Unsupported operators |
, |
Examples |
|
updatedBy()
Search for issues that were updated by a specific user, optionally within the specified time range. An update in this case includes creating an issue, updating any of the issue's fields, creating or deleting a comment, or editing a comment (only the last edit).
For the time range, use one of the following formats:
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w"
(weeks), or "d"
(days) to specify a date relative to the current time. Unlike some other functions, updatedBy
doesn't support values smaller then a day, and will always round them up to 1 day.
Syntax | updatedBy(user) updatedBy(user, dateFrom) updatedBy(user, dateFrom, dateTo) |
---|---|
Supported fields | Issuekey , and its aliases (id , issue , key ) |
Supported operators |
|
Unsupported operators | |
Examples |
|
votedIssues()
Perform searches based on issues for which you have voted. Also, see the Voter field.
This function can only be used by logged-in users.
Syntax | votedIssues() |
---|---|
Supported fields | Issue |
Supported operators |
|
Unsupported operators |
, |
Examples |
|
watchedIssues()
Perform searches based on issues that you are watching. Also, see the Watcher field.
This function can only be used by logged-in users.
Syntax | watchedIssues() |
---|---|
Supported fields | Issue |
Supported operators |
|
Unsupported operators |
, |
Examples |
|
withinCalendarHours()
Only applicable if Jira Service Management is installed and licensed.
Returns issues that have an SLA that is running according to the calendar.
For example, say your project has two SLAs that count Time to First Response. Some issues with this use a 9am-1pm calendar, and others use a 9am-5pm calendar. If an agent starts work at 3pm, they probably want to work on issues from the 9am-5pm agreement first. They can use withincalendarhours() to find all the issues where Time to First Response is running at 3pm.
Syntax | withinCalendarHours() |
---|---|
Supported fields | |
Supported operators | |
Unsupported operators |
|
Examples |
|