与 AND

用于整合多个查询条件, 允许你精炼查询条件。

注意，你可以使用 括号 来控制查询条件的执行顺序。

示例

• 查询"New office"项目中所有开放的问题:

  project = "New office" and status = "open"

• 查询所有分配给jsmith的紧急的开放问题:

  status = open and priority = urgent and assignee = jsmith

• 查询JRA项目中没有分配给jsmith的问题:

  project = JRA and assignee != jsmith

• 查找JRA和CONF项目中修复版本是3.14的问题:

  project in (JRA,CONF) and fixVersion = "3.14"

• 查找不是Jack,Jill,John报告的并且他们也不是经办人的问题:

  reporter not in (Jack,Jill,John) and assignee not in (Jack,Jill,John)

或 OR

用户整合多个查询条件, 允许你扩展查询条件。

注意，你可以使用 括号 来控制查询条件的执行顺序。

(注意: 也可以查看 在...之中(IN)章节, 使用更方便的方法搜索多个字段的值。)

示例

• 搜索报告人是jsmith或jbrown的问题:

  reporter = jsmith or reporter = jbrown

• 搜索已近逾期或没有设置到期日的问题:

  duedate < now() or duedate is empty

非 NOT

用于否定一个运算符或整个查询条件, 允许你优化查询条件。

注意，你可以使用 括号 来控制查询条件的执行顺序。

(注意: 也可以查看 不等于 ("!="), 不包括 ("!~"), 不再...之中 和 不是章节)

示例

• 搜索经办人不是jsmith的所有问题:

  not assignee = jsmith

• 搜索所有报告人不是jsmith或不是jbrown的问题:

  not (reporter = jsmith or reporter = jbrown)

空 EMPTY

用于搜索没有值的字段。 也可以查看空(NULL)。

注意 EMPTY 只能与 是(IS) 和 不是(IS NOT) 运算符结合使用。 要查看字段支持的运算符, 点击 #字段 。

示例

• 搜索所有没有到期日(DueDate)的问题 :

  duedate = empty

  or

  duedate is empty

空 NULL

用于搜索字段没有赋值的问题。 请查看 空(EMPTY)。

注意 NULL 只能用于支持 是(IS) 和 不是(IS NOT) 操作符的字段。 要了解字段支持哪些操作符, 请查看每个 字段 参考。

示例

• 查找所有没有设置 到期日(DueDate)的问题:

  duedate = null

  或

  duedate is null

排序 ORDER BY

用于对输出的结果，按照指定的字段排序。

默认情况下, 按照字段输出顺序排序。 你可以指定按照升序 ("asc") 或降序 ("desc")排列。

示例

• 查找所有没有设置 到期日(DueDate)的问题, 按照 创建日期(CreationDate)排序:

  duedate = empty order by created 

• 查找所有没有设置 到期日(DueDate)的问题，先按照 创建日期(CreationDate)排序，再按照 优先级(Priority) (从高到低)排列:

  duedate = empty order by created, priority desc

• 查找所有没有设置 到期日(DueDate)的问题，先按照 创建日期(CreationDate)排序，再按照 优先级(Priority)(从低到高)排列:

  duedate = empty order by created, priority asc

等于: =

"=" 运算符用于查找精确匹配字段值的问题。 (注意: 不能用于 文本 字段; 文本字段的匹配条件请使用 包含 运算符。)

要精确匹配多个字段值，请使用与(AND)将多个 "=" 表达式连接起来。

示例

• 查找由jsmith创建的所有问题:

  reporter = jsmith

• 查找由John Smith创建的所有问题:

  reporter = "John Smith"

不等于: !=

"!=" 运算符用于查找不等于指定字段值之外的问题。 (注意: 不能用于 文本 字段; 文本字段的否定条件请使用 不包含 ("!~") 运算符。)

注意输入 field != value 与输入 NOT field = value}}具有同等效果, 并且 {{field != EMPTY 与 {{field #IS_NOT EMPTY}}也具有同等效果。

示例

• 查找所有已经被分配经办人，但是经办人不是jsmith的问题:

  not assignee = jsmith

  or:

  assignee != jsmith

• 查找报告人不是jsmith的所有问题:

  reporter !=jsmith

• 查找你报告的，但经办人没有被分配给你的问题:

  reporter = currentUser() and assignee != currentUser()

• 查找已经被分配经办人，但报告人或经办人不是John Smith的问题:

  assignee != "John Smith" or reporter != "John Smith"

• 查找所有还没有分配经办人的问题:

  assignee is not empty

  或

  assignee != null

大于: >

">" 运算符用于差咋后比指定字段值大的问题。 不能用于 文本 字段。

注意 ">" 运算符只能用于支持排序的字段 (例如 日期字段和版本字段等)。 要了解字段支持哪些运算符, 请查看每个 字段 参考。

示例

• Find all issues with more than 4 votes:

  votes > 4

• Find all overdue issues:

  duedate < now() and resolution is empty

• Find all issues where priority is higher than "Normal":

  priority > normal

GREATER THAN EQUALS: >=

The ">=" operator is used to search for issues where the value of the specified field is greater than or equal to the specified value. Cannot be used with #text fields.

Note that the ">=" operator can only be used with fields which support ordering (e.g. date fields and version fields). To see a field's supported operators, check the individual #field reference.

示例

• Find all issues with 4 or more votes:

  votes >= 4

• Find all issues due on or after 31/12/2008:

  duedate >= "2008/12/31"

• Find all issues created in the last five days:

  created >= "-5d"

LESS THAN: <

The "<" operator is used to search for issues where the value of the specified field is less than the specified value. Cannot be used with #text fields.

Note that the "<" operator can only be used with fields which support ordering (e.g. date fields and version fields). To see a field's supported operators, check the individual #field reference.

示例

• Find all issues with less than 4 votes:

  votes < 4

LESS THAN EQUALS: <=

The "<=" operator is used to search for issues where the value of the specified field is less than or equal to than the specified value. Cannot be used with #text fields.

Note that the "<=" operator can only be used with fields which support ordering (e.g. date fields and version fields). To see a field's supported operators, check the individual #field reference.

示例

• Find all issues with 4 or fewer votes:

  votes <= 4

• Find all issues that have not been updated in the past month (30 days):

  updated <= "-4w 2d"

IN

The "IN" operator is used to search for issues where the value of the specified field is one of multiple specified values. The values are specified as a comma-delimited list, surrounded by parentheses.

Using "IN" is equivalent to using multiple #EQUALS (=) statements, but is shorter and more convenient. That is, typing reporter IN (tom, jane, harry) is the same as typing reporter = "tom" #OR reporter = "jane" #OR reporter = "harry".

示例

• Find all issues that were created by either jsmith or jbrown or jjones:

  reporter in (jsmith,jbrown,jjones)

• Find all issues where the Reporter or Assignee is either Jack or Jill:

  reporter in (Jack,Jill) or assignee in (Jack,Jill)

• Find all issues in version 3.14 or version 4.2:

  affectedVersion in ("3.14", "4.2")

NOT IN

The "NOT IN" operator is used to search for issues where the value of the specified field is not one of multiple specified values.

Using "NOT IN" is equivalent to using multiple #NOT_EQUALS (!=) statements, but is shorter and more convenient. That is, typing reporter NOT IN (tom, jane, harry) is the same as typing reporter != "tom" #AND reporter != "jane" #AND reporter != "harry".

示例

• Find all issues where the Reporter is not Jack, Jill or John:

  reporter not in (Jack,Jill,John)

• Find all issues where the FixVersion is not 'A', 'B', 'C' or 'D':

  FixVersion not in ( A, B, C, D)

• Find all issues where the FixVersion is not 'A', 'B', 'C' or 'D', or has not been specified:

  FixVersion not in ( A, B, C, D) or FixVersion is empty

CONTAINS: ~

The "~" operator is used to search for issues where the value of the specified field matches the specified value (either an exact match or a "fuzzy" match — see examples below). For use with text fields only, i.e.:

Note: when using the "~" operator, the value on the right-hand side of the operator can be specified using JIRA text-search syntax.

示例

• Find all issues where the Summary contains the exact phrase "full screen":

  summary ~ "\"full screen\""

• Find all issues where the Summary contains the word "win" (or derivatives of that word, such as "windows" or "winning"):

  summary ~ win

DOES NOT CONTAIN: !~

The "!~" operator is used to search for issues where the value of the specified field is not a "fuzzy" match for the specified value. For use with text fields only, i.e.:

Note: when using the "!~" operator, the value on the right-hand side of the operator can be specified using JIRA text-search syntax.

示例

• Find all issues where the Summary does not contain the word "run" (or derivatives of that word, such as "running" or "ran"):

  summary !~ run

IS

The "IS" operator can only be used with #EMPTY or #NULL. That is, it is used to search for issues where the specified field has no value.

Note that not all #fields are compatible with this operator; see the individual #field reference for details.

示例

• Find all issues that have no Fix Version:

  fixVersion is empty

  or

  fixVersion is null

IS NOT

The "IS NOT" operator can only be used with #EMPTY or #NULL. That is, it is used to search for issues where the specified field has a value.

Note that not all #fields are compatible with this operator; see the individual #field reference for details.

示例

• Find all issues that have one or more votes:

  votes is not empty

  or

  votes is not null

Affected Version

Search for issues that are assigned to a particular Affects Version(s). You can search by version name or version ID (i.e. the number that JIRA automatically allocates to a version).

Note: this field supports #auto-complete.

Syntax

affectedVersion

Field Type

VERSION

Supported Operators

Note that the comparison operators (e.g. ">") use the version order that has been set up by your project administrator, not a numeric or alphabetic order.

Supported Functions

When used with the #IN and #NOT_IN operators, affectedVersion supports:

• #releasedVersions()
• #unreleasedVersions()

示例

• Find issues with an AffectedVersion of 3.14:

  affectedVersion = "3.14"

  (Note that full-stops are reserved #characters, so they need to be surrounded by quote marks.)
• Find issues with an AffectedVersion of "Big Ted":

  affectedVersion = "Big Ted"

• Find issues with an AffectedVersion ID of 10350:

  affectedVersion = 10350

Assignee

Search for issues that are assigned to a particular user. You can search by the user's Full Name, ID or Email Address.

Note: this field supports #auto-complete.

Syntax

assignee

Field Type

USER

Supported Operators

Supported Functions

When used with the #IN and #NOT_IN operators, assignee supports:

• #membersOf()

When used with the #EQUALS and #NOT_EQUALS operators, assignee supports:

• #currentUser()

示例

• Search for issues that are assigned to John Smith:

  assignee = "John Smith"

  or

  assignee = jsmith

• Search for issues that are assigned by the user with email address "bob@mycompany.com":

  assignee = "bob@mycompany.com"

  (Note that full-stops and "@" symbols are reserved #characters, so the email address needs to be surrounded by quote-marks.)

Category

Search for issues that belong to projects in a particular Category.

Note: this field supports #auto-complete.

Syntax

category

Field Type

CATEGORY

Supported Operators

Supported Functions

n/a

示例

• Find issues that belong to projects in the "Alphabet Projects" Category:

   category = "Alphabet Projects"

Comment

Search for issues that have a Comment which contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support #auto-complete.

Syntax

comment

Field Type

TEXT

Supported Operators

Supported Functions

n/a

示例

• Find issues where a Comment contains text that matches "My PC is quite old" (i.e. a "fuzzy" match:

  comment ~ "My PC is quite old"

• Find issues where a Comment contains the exact phrase "My PC is quite old":

  comment ~ "\"My PC is quite old\""

Component

Search for issues that belong to a particular component(s) of a project. You can search by component name or component ID (i.e. the number that JIRA automatically allocates to a component).

Note: this field supports #auto-complete.

Syntax

component

Field Type

COMPONENT

Supported Operators

Supported Functions

When used with the #IN and #NOT_IN operators, component supports:

• #componentsLeadByUser()

示例

• Find issues in the "Comp1" or "Comp2" component:

   component in (Comp1, Comp2)

• Find issues in the "Comp1" and "Comp2" components:

   component in (Comp1) and component in (Comp2)

  or

   component = Comp1 and component = Comp2

• Find issues in the component with ID 20500:

  component = 20500

Created

Search for issues that were created on, before or after a particular date (or date range).

Note: this field does not support #auto-complete.

Syntax

created

Alias:

createdDate

Field Type

DATE

Supported Operators

Supported Functions

When used with the #EQUALS, #NOT_EQUALS, #GREATER_THAN, #GREATER_THAN_EQUALS, #LESS_THAN or #LESS_THAN_EQUALS operators, createdDate supports:

• #currentLogin()
• #lastLogin()
• #now()

示例

• Find all issues created on or before 12th December 2008 00:00:

  created <= "2008/12/12"

• Find issues created less than one day ago:

  created > "-1d"

• Find issues created in January 2009:

  created > "2008/12/31" and created < "2009/02/01"

• Find issues created on 15 January 2009:

  created > "2009/01/14" and created < "2009/01/16"

Custom Field

Only applicable if your JIRA administrator has created one or more Custom Fields.

Search for issues where a particular Custom Field has a particular value.

You can search by Custom Field name or Custom Field ID (i.e. the number that JIRA automatically allocates to an Custom Field).

Note:

• JIRA text-search syntax can be used with Custom Fields of type 'Text'.
• #auto-complete is supported for Custom Fields of type picker, group picker, select (except 'Cascading Select'), check-box and radio button fields.

Syntax

CustomFieldName

Alias:

cf[CustomFieldID]

Field Type

Depends on the Custom Field's configuration

Supported Operators

Different types of Custom Fields support different #operators. For the default Custom Field Types, the following operators are supported:

• Number and date/time fields:
  不能呈现 {include} 包含的页面未找到。
• Picker, select, check-box and radio button fields:
  不能呈现 {include} 包含的页面未找到。
• Text fields:
  不能呈现 {include} 包含的页面未找到。

Supported Functions

Different types of Custom Fields support different #functions. For the default Custom Field Types, the following functions are supported:

• Date/time fields: #currentLogin(), #lastLogin() and #now() (when used with any operator except #IS or #IS NOT)
• Version picker fields: #releasedVersions() and #unreleasedVersions() (when used with the #IN and #NOT_IN operators)

示例

• Find issues where the value of the "Location" Custom Field is "New York":

  location = "New York"

• Find issues where the value of the Custom Field with ID 10003 is "New York":

  cf[10003] = "New York"

• Find issues where the value of the "Location" Custom Field is "London" or "Milan" or "Paris":

  cf[10003] in ("London", "Milan", "Paris")

• Find issues where the "Location" Custom Field has no value:

  location != empty

Description

Search for issues where the Description contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support #auto-complete.

Syntax

description

Field Type

TEXT

Supported Operators

Supported Functions

n/a

示例

• Find issues where the Description contains text that matches "Please see screenshot" (i.e. a "fuzzy" match):

  description ~ "Please see screenshot"

• Find issues where the Description contains the exact phrase "Please see screenshot":

  description ~ "\"Please see screenshot\""

Due

Search for issues that were due on, before or after a particular date (or date range).

Note that Due Date relates to the date only (not to the time).

Note: this field does not support #auto-complete.

Syntax

due

Alias:

dueDate

Field Type

DATE

Supported Operators

Supported Functions

When used with the #EQUALS, #NOT_EQUALS, #GREATER_THAN, #GREATER_THAN_EQUALS, #LESS_THAN or #LESS_THAN_EQUALS operators, dueDate supports:

• #currentLogin()
• #lastLogin()
• #now()

示例

• Find all issues due on or before 31st December 2008:

  due <= "2008/12/31"

• Find issues that are due tomorrow:

  due = "1d"

• Find issues that were due in January 2009:

  due > "2008/12/31" and due < "2009/02/01"

• Find issues that were due on 15 January 2009:

  due > "2009/01/14" and due < "2009/01/16"

Environment

Search for issues where the Environment contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support #auto-complete.

Syntax

environment

Field Type

TEXT

Supported Operators

Supported Functions

n/a

示例

• Find issues where the Environment contains text that matches "Third floor" (i.e. a "fuzzy" match):

  environment ~ "Third floor"

• Find issues where the Environment contains the exact phrase "Third floor":

  environment ~ "\"Third floor\""

Filter

You can use a saved filter to narrow your search. You can search by filter name or filter ID (i.e. the number that JIRA automatically allocates to a saved filter).

Note:

• An #ORDER BY statement in your typed query will override an ORDER BY statement in the saved filter.
• You cannot run or save a filter that would cause an infinite loop (i.e. you cannot reference a saved filter if it eventually references your current filter).
• This field supports #auto-complete.

  Syntax

  filter

  Aliases:

  request

  savedFilter

  searchRequest

Field Type

FILTER

Supported Operators

Supported Functions

n/a

示例

• Search the results of the filter "My Saved Filter" (which has an ID of 12000) for issues assigned to the user jsmith:

  filter = "My Saved Filter" and assignee = jsmith

  or

  filter = 12000 and assignee = jsmith

Fix Version

Search for issues that are assigned to a particular Fix Version. You can search by version name or version ID (i.e. the number that JIRA automatically allocates to a version).

Note: this field supports #auto-complete.

Syntax

fixVersion

Field Type

VERSION

Supported Operators

Note that the comparison operators (e.g. ">") use the version order that has been set up by your project administrator, not a numeric or alphabetic order.

Supported Functions

When used with the #IN and #NOT_IN operators, fixVersion supports:

• #releasedVersions()
• #unreleasedVersions()

示例

• Find issues with a Fix Version of 3.14 or 4.2:

   fixVersion in ("3.14", "4.2")

  (Note that full-stops are reserved #characters, so they need to be surrounded by quote marks.)
• Find issues with a Fix Version of "Little Ted":

  fixVersion = "Little Ted"

• Find issues with a Fix Version ID of 10001:

  fixVersion = 10001

Issue Key

Search for issues with a particular Issue Key or Issue ID (i.e. the number that JIRA automatically allocates to an Issue).

Note: this field does not support #auto-complete.

Syntax

issueKey

Aliases:

id

issue

key

Field Type

ISSUE

Supported Operators

Supported Functions

When used with the #IN or #NOT_IN operators, issueKey supports:

• #issueHistory()
• #linkedIssues()
• #votedIssues()
• #watchedIssues()

示例

• Find the issue with key "ABC-123":

  issueKey = ABC-123 

Level

Only available if Issue Level Security has been enabled by your JIRA administrator.

Search for issues with a particular Security Level. You can search by Issue Security Level name or Issue Security Level ID (i.e. the number that JIRA automatically allocates to an Issue Security Level).

Note: this field supports #auto-complete.

Syntax

level

Field Type

SECURITY LEVEL

Supported Operators

Supported Functions

n/a

示例

• Search for issues with a Security Level of "Really High" or "level1":

  level in ("Really High", level1)

• Search for issues with a Security Level ID of 123:

  level = 123

Original Estimate

Only available if time-tracking has been enabled by your JIRA administrator.

Search for issues where the Original Estimate is set to a particular value (i.e. a number, not a date or date range).

Use "w", "d", "h" and "m" to specify weeks, days, hours or minutes.

Note: this field does not support #auto-complete.

Syntax

originalEstimate

Alias:

timeOriginalEstimate

Field Type

DURATION

Supported Operators

Supported Functions

n/a

示例

• Find issues with an Original Estimate of 1 hour:

  originalEstimate = 1h

• Find issues with an Original Estimate of more than 2 days:

  originalEstimate > 2d

Parent

Only available if sub-tasks have been enabled by your JIRA administrator.

Search for all sub-tasks of a particular issue. You can search by Issue Key or by Issue ID (i.e. the number that JIRA automatically allocates to an Issue).

Note: this field does not support #auto-complete.

Syntax

parent

Field Type

ISSUE

Supported Operators

Supported Functions

n/a

示例

• Find issues that are sub-tasks of issue TEST-1234:

  parent = TEST-1234

Priority

Search for issues with a particular Priority. You can search by Priority name or Priority ID (i.e. the number that JIRA automatically allocates to a Priority).

Note: this field supports #auto-complete.

Syntax

priority

Field Type

PRIORITY

Supported Operators

Supported Functions

n/a

示例

• Find issues with a Priority of "High":

   priority = High

• Find issues with a Priority ID of 10000:

  priority = 10000

Project

Search for issues that belong to a particular Project

You can search by Project Name, by Project Key or by Project ID (i.e. the number that JIRA automatically allocates to a project).

Note: this field supports #auto-complete.

Syntax

project

Field Type

PROJECT

Supported Operators

Supported Functions

When used with the #IN and #NOT_IN operators, project supports:

• #projectsLeadByUser()
• #projectsWhereUserHasPermission()
• #projectsWhereUserHasRole()

示例

• Find issues that belong to the Project that has the name "ABC Project":

   project = "ABC Project" 

• Find issues that belong to the Project that has the key "ABC":

  project = "ABC"

• Find issues that belong to the Project that has the ID "1234":

  project = 1234

Remaining Estimate

Only available if time-tracking has been enabled by your JIRA administrator.

Search for issues where the Remaining Estimate is set to a particular value (i.e. a number, not a date or date range).

Use "w", "d", "h" and "m" to specify weeks, days, hours or minutes.

Note: this field does not support #auto-complete.

Syntax

remainingEstimate

Alias:

timeEstimate

Field Type

DURATION

Supported Operators

Supported Functions

n/a

示例

• Find issues with a Remaining Estimate of more than 4 hours:

   remainingEstimate > 4h 

Reporter

Search for issues that were reported by (i.e. created by) a particular user.

You can search by the user's Full Name, ID or Email Address.

Note: this field supports #auto-complete.

Syntax

reporter

Field Type

USER

Supported Operators

Supported Functions

When used with the #IN and #NOT_IN operators, reporter supports:

• #membersOf()

When used with the #EQUALS and #NOT_EQUALS operators, reporter supports:

• #currentUser()

示例

• Search for issues that were created by Jill Jones:

  reporter = "Jill Jones"

  or

  reporter = jjones

• Search for issues that were created by the user with email address "bob@mycompany.com":

  assignee = "bob@mycompany.com"

  (Note that full-stops and "@" symbols are reserved #characters, so the email address needs to be surrounded by quote-marks.)

Resolution

Search for issues that have a particular Resolution

You can search by Resolution name or Resolution ID (i.e. the number that JIRA automatically allocates to a Resolution).

Note: this field supports #auto-complete.

Syntax

resolution

Field Type

RESOLUTION

Supported Operators

Supported Functions

n/a

示例

• Find issues with a Resolution of "Cannot Reproduce" or "Won't Fix":

   resolution in ("Cannot Reproduce", "Won't Fix")

• Find issues with a Resolution ID of 5:

  resolution = 5

• Find issues that do not have a Resolution:

  resolution = unresolved

Resolved

Search for issues that were resolved on, before or after a particular date (or date range).

Note: this field does not support #auto-complete.

Syntax

resolved

Alias:

resolutionDate

Field Type

DATE

Supported Operators

Supported Functions

When used with the #EQUALS, #NOT_EQUALS, #GREATER_THAN, #GREATER_THAN_EQUALS, #LESS_THAN or #LESS_THAN_EQUALS operators, resolved supports:

• #currentLogin()
• #lastLogin()
• #now()

示例

• Find all issues that were resolved on or before 31st December 2008 00:00:

  resolved <= "2008/12/31"

• Find issues that were resolved in January 2009:

  resolved > "2008/12/31" and resolved < "2009/02/01"

• Find issues that were resolved on 15 January 2009:

  resolved > "2009/01/14" and resolved < "2009/01/16"

• Find issues that were resolved in the last hour:

  resolved > -1h

Status

Search for issues that have a particular Status.

You can search by Status name or Status ID (i.e. the number that JIRA automatically allocates to a Status).

Note: this field supports #auto-complete.

Syntax

status

Field Type

STATUS

Supported Operators

Supported Functions

n/a

示例

• Find issues with a Status of "Open":

   status = Open

• Find issues with a Status ID of 1:

  status = 1

Summary

Search for issues where the Summary contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support #auto-complete.

Syntax

summary

Field Type

TEXT

Supported Operators

Supported Functions

n/a

示例

• Find issues where the Summary contains text that matches "Error saving file" (i.e. a "fuzzy" match):

  summary ~ "Error saving file"

• Find issues where the Summary contains the exact phrase "Error saving file":

  summary ~ "\"Error saving file\""

Text

This is a "master-field" that allows you to search all text fields, i.e.:

Note: The text master-field can only be used with the #CONTAINS operator ("~" and "!~").

Syntax

text

Field Type

TEXT

Supported Operators

Supported Functions

n/a

示例

• Find issues where a text field matches the word "Fred":

  text ~ "Fred"

  or

  text ~ Fred

• Find all issues where a text field contains the exact phrase "full screen":

  text ~ "\"full screen\""

Type

Search for issues that have a particular Issue Type.

You can search by Issue Type name or Issue Type ID (i.e. the number that JIRA automatically allocates to an Issue Type).

Note: this field supports #auto-complete.

Syntax

type

Alias:

issueType

Field Type

ISSUE_TYPE

Supported Operators

Supported Functions

n/a

示例

• Find issues with an Issue Type of "Bug":

  type = Bug

• Find issues with an Issue Type of "Bug" or "Improvement":

   issueType in (Bug,Improvement)

• Find issues with an Issue Type ID of 2:

  issueType = 2

Time Spent

Only available if time-tracking has been enabled by your JIRA administrator.

Search for issues where the Time Spent is set to a particular value (i.e. a number, not a date or date range).

Use "w", "d", "h" and "m" to specify weeks, days, hours or minutes.

Note: this field does not support #auto-complete.

Syntax

timeSpent

Field Type

DURATION

Supported Operators

Supported Functions

n/a

示例

• Find issues where the Time Spent is more than 5 days:

  timeSpent > 5d

Updated

Search for issues that were last updated on, before or after a particular date (or date range).

Note: this field does not support #auto-complete.

Syntax

updated

Alias:

updatedDate

Field Type

DATE

Supported Operators

Supported Functions

When used with the #EQUALS, #NOT_EQUALS, #GREATER_THAN, #GREATER_THAN_EQUALS, #LESS_THAN or #LESS_THAN_EQUALS operators, updated supports:

• #currentLogin()
• #lastLogin()
• #now()

示例

• Find issues that were updated on or before 12th December 2008 00:00:

  updated <= "2008/12/12"

• Find issues that were updated more than two weeks ago:

  updated < "-2w"

• Find issues that were updated on 15 January 2009:

  updated > "2009/01/14" and updated < "2009/01/16"

• Find issues that were updated in January 2009:

  updated > "2008/12/31" and updated < "2009/02/01"

Voter

Search for issues for which a particular user has voted. You can search by the user's Full Name, ID or Email Address. Note that you can only find issues for which you have the "View Voters and Watchers" permission, unless you are searching for your own votes. See also #votedIssues.

Note: this field supports #auto-complete.

Syntax

voter

Field Type

USER

Supported Operators

Supported Functions

When used with the #IN and #NOT_IN operators, voter supports:

• #membersOf()

When used with the #EQUALS and #NOT_EQUALS operators, voter supports:

• #currentUser()

示例

• Search for issues for which you have voted:

  voter = currentUser()

• Search for issues for which the user "jsmith" has voted:

  voter = "jsmith"

• Search for issues for which a member of the group "jira-developers" has voted:

  voter in membersOf("jira-developers")

Votes

Search for issues with a specified number of votes.

Note: this field does not support #auto-complete.

Syntax

votes

Field Type

NUMBER

Supported Operators

Supported Functions

n/a

示例

• Find all issues that have 12 or more votes:

  votes >= 12

Watcher

Search for issues that a particular user is watching. You can search by the user's Full Name, ID or Email Address. Note that you can only find issues for which you have the "View Voters and Watchers" permission, unless you are searching for issues where you are the watcher. See also #watchedIssues.

Note: this field supports #auto-complete.

Syntax

voter

Field Type

USER

Supported Operators

Supported Functions

When used with the #IN and #NOT_IN operators, watcher supports:

• #membersOf()

When used with the #EQUALS and #NOT_EQUALS operators, watcher supports:

• #currentUser()

示例

• Search for issues that you are watching:

  watcher = currentUser()

• Search for issues that the user "jsmith" is watching:

  watcher = "jsmith"

• Search for issues that are being watched by a member of the group "jira-developers":

  watcher in membersOf("jira-developers")

Work Ratio

Only available if time-tracking has been enabled by your JIRA administrator.

Search for issues where the Work Ratio has a particular value.

Work Ratio is calculated as follows: workRatio = #timeSpent / #originalEstimate) x 100

Note: this field does not support #auto-complete.

Syntax

workRatio

Field Type

NUMBER

Supported Operators

Supported Functions

n/a

示例

• Find issues on which more than 75% of the Original Estimate has been spent:

   workRatio > 75

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)

or

cascadeOption(parentOption,childOption)

Supported Field Types

CASCADING_OPTION

Supported Operators

示例

• Find issues where a custom field ("Location") has the value "USA" for the first tier and "New York" for the second tier:

  location in cascadeOption("USA","New York")

• Find issues where a custom field ("Location") has the value "USA" for the first tier and any value (or no value) for the second tier:

  location in cascadeOption("USA")

• Find issues where a custom field ("Location") has the value "USA" for the first tier and no value for the second tier:

  location in cascadeOption("USA",none)

• Find issues where a custom field ("Location") has no value for the first tier and no value for the second tier:

  location in cascadeOption(none)

• Find issues where a custom field ("Referrer") has the value "none" for the first tier and "none" for the second tier:

  referrer in cascadeOption("\"none\"","\"none\"")

• Find issues where a custom field ("Referrer") has the value "none" for the first tier and no value for the second tier:

  referrer in cascadeOption("\"none\"",none)

componentsLeadByUser()

Find issues in components that are lead 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.

Note that if you are not logged in to JIRA, a user must be specified.

Syntax

componentsLeadByUser()

or

componentsLeadByUser(username)

Supported Field Types

COMPONENT

Supported Operators

示例

• Find open issues in components that are lead by you:

  component in componentsLeadByUser() AND status = Open

• Find open issues in components that are lead by Bill:

  component in componentsLeadByUser(bill) AND status = Open

currentLogin()

Perform searches based on the time at which the current user's session began. See also #lastLogin.

Syntax

currentLogin()

Supported Field Types

DATE

Supported Operators

示例

• Find issues that have been created during my current session:

  created > currentLogin()

currentUser()

Perform searches based on the currently logged-in user.

Note that this function can only be used by logged-in users. So if you are creating a saved filter that you expect to be used by anonymous users, do not use this function.

Syntax

currentUser()

Supported Field Types

USER

Supported Operators

示例

• Find issues that are assigned to me:

  assignee = currentUser()

• Find issues that were reported to me but are not assigned to me:

  reporter = currentUser() and assignee != currentUser()

issueHistory()

Find issues that you have recently viewed, i.e. issues that are in the 'Recent Issues' section of the 'Issues' drop-down menu.

Note:

• issueHistory() returns up to 50 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.

Syntax

issueHistory()

Supported Field Types

ISSUE

Supported Operators

示例

• Find issues which I have recently viewed, that are assigned to me:

  issue in issueHistory() AND assignee = currentUser()

lastLogin()

Perform searches based on the time at which the current user's previous session began. See also #currentLogin.

Syntax

currentLogin()

Supported Field Types

DATE

Supported Operators

示例

• Find issues that have been created during my last session:

  created > lastLogin()

linkedIssues()

Perform searches based on issues which 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)

or

linkedIssues(issueKey,linkType)

Supported Field Types

ISSUE

Supported Operators

示例

• Find issues that are linked to a particular issue:

  issue in linkedIssues(ABC-123)

• Find issues that are linked to a particular issue via a particular type of link:

  issue in linkedIssues(ABC-123,"is duplicated by")

membersOf()

Perform searches based on the members of a particular group.

Syntax

membersOf(Group)

Supported Field Types

USER

Supported Operators

示例

• Find issues where the Assignee is a member of the group "jira-developers":

  assignee in membersOf("jira-developers")

• Search through multiple groups and a specific user, e.g:

  reporter in membersOf("jira-developers") or reporter in membersOf("jira-administrators") or reporter=jsmith

• Search for a particular group, but exclude a particular member or members, e.g.:

  assignee in membersOf(QA) and assignee not in ("John Smith","Jill Jones")

• Exclude members of a particular group:

  assignee not in membersOf(QA)

now()

Perform searches based on the current time.

Syntax

now()

Supported Field Types

DATE

Supported Operators

示例

• Find issues that are overdue:

  duedate < now() and status not in (closed, resolved) 

projectsLeadByUser()

Find issues in projects that are lead by a specific user.

You can optionally specify a user, or if the user is omitted the current user will be used.

Note that if you are not logged in to JIRA, a user must be specified.

Syntax

projectsLeadByUser()

or

projectsLeadByUser(username)

Supported Field Types

PROJECT

Supported Operators

示例

• Find open issues in projects that are lead by you:

  project in projectsLeadByUser() AND status = Open

• Find open issues in projects that are lead by Bill:

  project in projectsLeadByUser(bill) AND status = Open

projectsWhereUserHasPermission()

Find issues in projects where you have a specific permission.

Note that this function is only available if you are logged in to JIRA.

Syntax

projectsWhereUserHasPermission(permission)

For the permission parameter you can specify any of the following:

Supported Field Types

PROJECT

Supported Operators

示例

• Find open issues in projects where you have the "Resolve Issues" permission:

  project in projectsWhereUserHasPermission("Resolve Issues") AND status = Open

projectsWhereUserHasRole()

Find issues in projects where you have a specific role.

Note that this function is only available if you are logged in to JIRA.

Syntax

projectsWhereUserHasRole(rolename)

Supported Field Types

PROJECT

Supported Operators

示例

• Find open issues in projects where you have the "Developers" role:

  project in projectsWhereUserHasRole("Developers") AND status = Open

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.

Syntax

releasedVersions()

or

releasedVersions(project)

Supported Field Types

VERSION

Supported Operators

示例

• Find issues whose #FixVersion is a released version of the ABC project:

  fixVersion in releasedVersions(ABC)

• Find issues that relate to released versions of the ABC project:

  affectedVersion in releasedVersions(ABC)

  or

  fixVersion in releasedVersions(ABC)

standardIssueTypes()

Perform searches based on "standard" Issue Types, that is, search for issues which are not sub-tasks.

Syntax

standardIssueTypes()

Supported Field Types

ISSUE_TYPE

Supported Operators

示例

• Find issues that are not subtasks (i.e. issues whose Issue Type is a standard issue type, not a subtask issue type):

  issuetype in standardIssueTypes()

subtaskIssueTypes()

Perform searches based on issues which are sub-tasks.

Syntax

subtaskIssueTypes()

Supported Field Types

ISSUE_TYPE

Supported Operators

示例

• Find issues that are subtasks (i.e. issues whose Issue Type is a subtask issue type):

  issuetype in subtaskIssueTypes()

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.

Syntax

unreleasedVersions()

or

unreleasedVersions(project)

Supported Field Types

VERSION

Supported Operators

示例

• Find issues whose #FixVersion is an unreleased version of the ABC project:

  fixVersion in unreleasedVersions(ABC)

• Find issues that relate to unreleased versions of the ABC project:

  affectedVersion in unreleasedVersions(ABC)

  or

  fixVersion in unreleasedVersions(ABC)

votedIssues()

Perform searches based on issues for which you have voted. Also see the #Voter field.

Note that this function can only be used by logged-in users.

Syntax

votedIssues()

Supported Field Types

ISSUE

Supported Operators

示例

• Find issues that you have voted for:

  issue in votedIssues()

watchedIssues()

Perform searches based on issues which you are watching. Also see the #Watcher field.

Note that this function can only be used by logged-in users.

Syntax

watchedIssues()

Supported Field Types

ISSUE

Supported Operators

示例

• Find issues that you are watching:

  issue in watchedIssues()

Supported Field Types

ISSUE

Supported Operators

示例

• Find issues that you have recently viewed:

  issue in issueHistory()

The list of auto-complete suggestions is displayed alphabetically and includes the first 15 matches. Note that auto-complete suggestions are not offered for #function parameters.

Auto-complete suggestions are not offered for all fields. Check the #fields reference to see which fields support auto-complete.

If you type a space at the start of your query...

...JIRA will offer a list of all available fields, e.g.:

If you type one or more characters...

...JIRA will offer a list of matching fields, e.g.:

If you type a field then a space...

...JIRA will offer a list of valid #operators, e.g.:

If you type a field, then an operator, then a space...

...JIRA will offer a list of valid values, e.g.:

If you type a field, then an operator, then one or more characters...

...JIRA will offer a list of valid values (if your #field supports this) and valid functions for the field/operator combination, e.g.: