AND

複数の句を組み合わせて検索を絞り込むために使用します。

Note that you can use parentheses to control the order in which clauses are executed.

例

• "New office" プロジェクト内のすべてのオープンな課題を検索:

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

• jsmith に割り当てられたオープンかつ緊急のすべての課題を検索:

  status = open and priority = urgent and assignee = jsmith

• jsmith に割り当てられていない、特定のプロジェクト内のすべての課題を検索:

  project = JRA and assignee != jsmith

• 複数のプロジェクトにおいて、複数のバージョン番号で構成される特定のリリースに対するすべての課題を検索:

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

• 報告者と担当者が Jack、Jill、John のいずれでもないすべての課題を検索:

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

^top of keywords | ^^top of topic

または

複数の句を組み合わせて検索範囲を広げるために使用します。

Note that you can use parentheses to control the order in which clauses are executed.

(Note: also see IN, which can be a more convenient way to search for multiple values of a field.)

例

• jsmith または jbrown のいずれかが作成したすべての課題を検索:

  reporter = jsmith or reporter = jbrown

• 期限切れまたは期限が設定されていないすべての課題を検索:

  duedate < now() or duedate is empty

^top of keywords | ^^top of topic

NOT

Used to negate individual clauses or a complex JQL query (a query made up of more than one clause) using parentheses, allowing you to refine your search.

(Note: also see NOT EQUALS ("!="), DOES NOT CONTAIN ("!~"), NOT IN and IS NOT.)

例

• jsmith 以外のすべてのユーザーに割り当てられたすべての課題を検索:

  not assignee = jsmith

• jsmith または jbrown が作成していないすべての課題を検索:

  not (reporter = jsmith or reporter = jbrown)

^top of keywords | ^^top of topic

EMPTY

Used to search for issues where a given field does not have a value. See also NULL.

Note that EMPTY can only be used with fields that support the IS and IS NOT operators. To see a field's supported operators, check the individual field reference.

例

• Find all issues without a DueDate:

  duedate = empty

  または

  duedate is empty

^top of keywords | ^^top of topic

NULL

Used to search for issues where a given field does not have a value. See also EMPTY.

Note that NULL can only be used with fields that support the IS and IS NOT operators. To see a field's supported operators, check the individual field reference.

例

• Find all issues without a DueDate:

  duedate = null

  または

  duedate is null

^top of keywords | ^^top of topic

ORDER BY

検索結果の並び順の基準として使用する値を持つフィールドを指定するために使用します。

既定では、フィールド独自の並び順が使用されます。昇順 (asc) または降順 (desc) を指定することで、この順序を上書きできます。

例

• Find all issues without a DueDate, sorted by CreationDate:

  duedate = empty order by created

• Find all issues without a DueDate, sorted by CreationDate, then by Priority (highest to lowest):

  duedate = empty order by created, priority desc

• Find all issues without a DueDate, sorted by CreationDate, then by Priority (lowest to highest):

  duedate = empty order by created, priority asc

^top of keywords | ^^top of topic

EQUALS: =

The "=" operator is used to search for issues where the value of the specified field exactly matches the specified value. (Note: cannot be used with text fields; see the CONTAINS operator instead.)

To find issues where the value of a specified field exactly matches multiple values, use multiple "=" statements with the AND operator.

例

• jsmith が作成したすべての課題を検索:

  reporter = jsmith

• John Smith が作成したすべての課題を検索:

  reporter = "John Smith"

^top of operators | ^^top of topic

NOT EQUALS: !=

The "!=" operator is used to search for issues where the value of the specified field does not match the specified value. (Note: cannot be used with text fields; see the DOES NOT MATCH ("!~") operator instead.)

Note that typing field != value is the same as typing NOT field = value, and that field != EMPTY is the same as field IS_NOT EMPTY.

The "!=" operator will not match a field that has no value (i.e. a field that is empty). For example, component != fred will only match issues that have a component and the component is not "fred". To find issues that have a component other than "fred" or have no component, you would need to type: component != fred or component is empty.

例

• jsmith 以外のすべてのユーザーに割り当てられたすべての課題を検索:

  not assignee = jsmith

  または

  assignee != jsmith

• jsmith に割り当てられていないすべての課題を検索:

  assignee != jsmith or assignee is empty

• 自分以外が報告した、自分に割り当てられていないすべての課題を検索:

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

• 報告社または担当者が John Smith 以外のすべてのユーザーであるすべての課題を検索:

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

• 未割り当てのすべての課題を検索:

  assignee is not empty

  または

  assignee != null

^top of operators | ^^top of topic

GREATER THAN: >

The ">" operator is used to search for issues where the value of the specified field is greater 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.

例

• 投票数が 4 票より多いすべての課題を検索:

  votes > 4

• 期限切れのすべての課題を検索:

  duedate < now() and resolution is empty

• 優先度が "Normal" より高いすべての課題を検索:

  priority > normal

^top of operators | ^^top of topic

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.

例

• 投票数が 4 票以上のすべての課題を検索:

  votes >= 4

• 期限が 2008 年 12 月 31 日以降のすべての課題を検索:

  duedate >= "2008/12/31"

• 過去 5 日間に作成されたすべての課題を検索:

  created >= "-5d"

^top of operators | ^^top of topic

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.

例

• 投票数が 4 票より少ないすべての課題を検索:

  votes < 4

^top of operators | ^^top of topic

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.

例

• 投票数が 4 票以下のすべての課題を検索:

  votes <= 4

• 過去 1 ヶ月間 (30 日間) 更新されなかったすべての課題を検索:

  updated <= "-4w 2d"

^top of operators | ^^top of topic

IN

"IN" 演算子は、指定したフィールドの値が対象となる複数の値のいずれかである課題を検索するために使用します。値は、括弧で囲んだカンマ区切りのリスト形式で指定します。

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".

例

• jsmith、jbrown、jjones のいずれかが作成したすべての課題を検索:

  reporter in (jsmith,jbrown,jjones)

• 報告者または担当者が Jack または Jill であるすべての課題を検索:

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

• バージョン 3.14 またはバージョン 4.2 のすべての課題を検索:

  affectedVersion in ("3.14","4.2")

^top of operators | ^^top of topic

NOT IN

"NOT IN" 演算子は、指定したフィールドの値が対象となる複数の値に含まれない課題を検索するために使用します。

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".

The "NOT IN" operator will not match a field that has no value (i.e. a field that is empty). For example, assignee not in (jack,jill) will only match issues that have an assignee and the assignee is not "jack" or "jill". To find issues that are assigned to someone other than "jack" or "jill" or are unassigned, you would need to type: assignee not in (jack,jill) or assignee is empty.

例

• Assignee (担当者) が Jack、Jill または John の課題をすべて検索する:

  assignee not in (Jack,Jill,John)

• Assignee (担当者) が、Jack、Jill、John 以外の課題をすべて検索する:

  assignee not in (Jack,Jill,John) or assignee is empty

• FixVersion (修正バージョン) が、'A'、'B'、'C'、'D' 以外の課題をすべて検索する:

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

• FixVersion (修正バージョン) が、'A'、'B'、'C'、'D' 以外、または指定されていない課題をすべて検索する:

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

^top of operators | ^^top of topic

CONTAINS: ~

"~" 演算子は、指定したフィールドの値が指定した値と一致する課題の検索に使用します (完全一致またはあいまい一致。以降の例を参照)。次のようなテキスト フィールドでのみ使用できます。

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

例

• 要約に "win" の単語 (または "wins" などの指定した語を含む単語) を含むすべての課題を検索:

  summary ~ win

• Find all issues where the Summary contains a wild-card match for the word "win":

  summary ~ "win*"

• Find all issues where the Summary contains the exact phrase "full screen" (see Reserved Characters for details on how to escape quote-marks and other special characters):

  summary ~ "\"full screen\""

^top of operators | ^^top of topic

DOES NOT CONTAIN: !~

"!~" 演算子は、指定したフィールドの値が指定した値のあいまい一致に該当しない課題の検索に使用します。次のようなテキスト フィールドでのみ使用できます。

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

例

• 要約に "run" の単語 (または "running" などの指定した語を含む単語) を含まないすべての課題を検索:

  summary !~ run

^top of operators | ^^top of topic

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.

例

• 修正バージョンを持たないすべての課題を検索:

  fixVersion is empty

  または

  fixVersion is null

^top of operators | ^^top of topic

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.

例

• 投票数が 1 票以上のすべての課題を検索:

  votes is not empty

  または

  votes is not null

^top of operators | ^^top of topic

WAS

The "WAS" operator is used to find issues that currently have, or previously had, the specified value for the specified field.

例

• 現在または過去のステータスが "n Progress (進行中)" である (であった) 課題を検索する:

  status WAS "In Progress"

• Joe Smith が 2 月 2 日より前に解決した課題を検索:

  status WAS "Resolved" BY jsmith BEFORE "02/02/2011"

• Joe Smith が 2010 年に解決した課題を検索:

  status WAS "Resolved" BY jsmith DURING ("01/01/2010","01/01/2011")

^top of operators | ^^top of topic

WAS IN

The "WAS IN" operator is used to find issues that currently have, or previously had, any of multiple specified values for the specified field. The values are specified as a comma-delimited list, surrounded by parentheses.

Using "WAS IN" is equivalent to using multiple WAS statements, but is shorter and more convenient. That is, typing status WAS IN ('Resolved', 'Closed') is the same as typing status WAS "Resolved" OR status WAS "Closed".

例

• 現在または過去のステータスが "Resolved" または "In Progress" であるすべての課題を検索:

  status WAS IN ("Resolved","In Progress")

^top of operators | ^^top of topic

WAS NOT IN

"WAS NOT IN" 演算子は、指定したフィールドの値が対象の複数の値のいずれかを持ったことがない課題を検索するために使用します。

Using "WAS NOT IN" is equivalent to using multiple WAS_NOT statements, but is shorter and more convenient. That is, typing status WAS NOT IN ("Resolved","In Progress") is the same as typing status WAS NOT "Resolved" AND status WAS NOT "In Progress".

例

• "Resolved" または "In Progress" のステータスを持ったことがないすべての課題を検索:

  status WAS NOT IN ("Resolved","In Progress")

• 2 月 2 日より前に "Resolved" または "In Progress" のステータスを持たなかったすべての課題を検索:

  status WAS NOT IN ("Resolved","In Progress") BEFORE "02/02/2011"

^top of operators | ^^top of topic

WAS NOT

"WAS NOT" 演算子は、指定したフィールドが対象の値を持ったことがない課題の検索に使用します。

例

• ステータスが "In Progress (進行中)" ではなく、これまでにもなったことがない課題を検索する:

  status WAS NOT "In Progress"

• 2 月 2 日より前に "In Progress" ステータスを持たなかった課題を検索:

  status WAS NOT "In Progress" BEFORE "02/02/2011"

^top of operators | ^^top of topic

CHANGED

This feature is only available in JIRA 4.4.3 and later.

The "CHANGED" operator is used to find issues that have a value which had changed for the specified field.

この演算子では次の述部を使用できます:

• FROM "古い値"

• TO "新しい値"

• BY "ユーザー名"

• ON "日付"

• DURING ("日付1","日付2")

• BEFORE "日付"

• AFTER "日付"

(Note: This operator can currently be used with the Status, Assignee, Priority, Reporter, Resolution and Fix Version fields only.)

例

• 担当者が変更された課題を検索:

  assignee CHANGED

• ステータスが "In Progress" から "Open " に変更された課題を検索:

  status CHANGED FROM "In Progress" TO "Open"

• 現在の週の間にユーザー "freddo" が Priority を変更した課題を検索:

  priority CHANGED BY freddo BEFORE endOfWeek() AFTER startOfWeek()

^top of operators | ^^top of topic

対象バージョン

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.

構文

affectedVersion

フィールド タイプ

VERSION

サポートされる演算子

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.

サポートされる関数

例

• AffectedVersion (対象バージョン) が 3.14 の課題を検索する:

  affectedVersion = "3.14"

  (Note that full-stops are reserved characters, so they need to be surrounded by quote marks.)

• AffectedVersion (対象バージョン) が "Big Ted" の課題を検索する:

  affectedVersion = "Big Ted"

• AffectedVersion ID (対象バージョン ID) が 10350 の課題を検索する:

  affectedVersion = 10350

^top of fields | ^^top of topic

担当者

特定のユーザーに割り当てられた課題を検索します。検索条件にはユーザーのフルネーム、ID またはメールアドレスを使用できます。

Note: this field supports auto-complete.

構文

担当者

フィールド タイプ

USER

サポートされる演算子

サポートされる関数

例

• John Smith に割り当てられた課題を検索する:

  assignee = "John Smith"

  または

  assignee = jsmith

• John Smith に現在割り当てられている、または過去に割り当てられていた課題を検索する:

  assignee WAS "John Smith"

  または

  assignee WAS jsmith

• Find 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.)

^top of fields | ^^top of topic

カテゴリ

特定のカテゴリー内のプロジェクトに所属する課題を検索します。

Note: this field supports auto-complete.

構文

category

フィールド タイプ

CATEGORY

サポートされる演算子

サポートされる関数

n/a

例

• "Alphabet Projects" カテゴリーのプロジェクトに所属する課題を検索する:

  category = "Alphabet Projects"

^top of fields | ^^top of topic

コメント

Comment (コメント) に特定のテキストが含まれる課題を検索します。

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

構文

comment

フィールド タイプ

TEXT

サポートされる演算子

サポートされる関数

n/a

例

• Comment (コメント) に "My PC is quite old (自分の PC は非常に古い)" と一致するテキストが含まれる課題を検索する (例: 「あいまい」一致):

  comment ~ "My PC is quite old"

• Comment (コメント) に "My PC is quite old (自分の PC は非常に古い)" との完全一致が含まれる課題を検索する:

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

^top of fields | ^^top of topic

コンポーネント

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.

構文

component

フィールド タイプ

COMPONENT

サポートされる演算子

サポートされる関数

When used with the IN and NOT IN operators, component supports:

• componentsLeadByUser()

例

• "Comp1" または "Comp2" コンポーネント内の課題を検索する:

  component in (Comp1, Comp2)

• "Comp1" および "Comp2" コンポーネント内の課題を検索する:

  component in (Comp1) and component in (Comp2)

  または

  component = Comp1 and component = Comp2

• ID が 20500 のコンポーネント内で課題を検索する:

  component = 20500

^top of fields | ^^top of topic

作成日

Search for issues that were created on, before or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).

Note: this field does not support auto-complete.

構文

created

Alias (エイリアス):

createdDate

フィールド タイプ

DATE

サポートされる演算子

サポートされる関数

例

• Find all issues created before 12th December 2010:

  created < "2010/12/12"

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

  created <= "2010/12/13"

• 2010 年 12 月 12 日 2:00pm より前に作成された課題をすべて検索する:

  created > "2010/12/12" and created < "2010/12/12 14:00"

• 1 日以内に作成された課題を検索する:

  created > "-1d"

• 2011 年 1 月に作成された課題を検索する:

  created > "2011/01/01" and created < "2011/02/01"

• 2011 年 1 月 15 日に作成された課題を検索する:

  created > "2011/01/15" and created < "2011/01/16"

^top of fields | ^^top of topic

カスタム フィールド

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

特定のカスタム フィールドに特定の値が入力された課題を検索します。

検索条件にはカスタム フィールド名またはカスタム フィールド ID (例: JIRA がカスタム フィールドに自動的に割り当てた番号) を使用できます。

注意:

• 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.

構文

CustomFieldName

Alias (エイリアス):

cf[CustomFieldID]

フィールド タイプ

Depends on the Custom Field's configuration

サポートされる演算子

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

• 数字および日付/ 時刻フィールド:
• ピッカー、選択、チェックボックス、ラジオ ボタン フィールド:
• テキスト フィールド:

サポートされる関数

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

• Date/time fields:
• Version picker fields:

例

• "Location (場所)" カスタム フィールドの値が "New York" の課題を検索する:

  location = "New York"

• ID が 10003 で、カスタム フィールドの値が "New York" の課題を検索する:

  cf[10003] = "New York"

• "Location (場所)" カスタム フィールドの値が "London"、"Milan" または "Paris" の課題を検索する:

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

• "Location (場所)" カスタム フィールドの値がない課題を検索する:

  location != empty

^top of fields | ^^top of topic

説明

Search for issues where the Description contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

構文

description

フィールド タイプ

TEXT

サポートされる演算子

サポートされる関数

n/a

例

• Description (説明) に "Please see screenshot (スクリーンショットを参照)" と一致するテキストが含まれる課題を検索する (例: 「あいまい」一致):

  description ~ "Please see screenshot"

• Description (説明) に "Please see screenshot (スクリーンショットを参照)" との完全一致が含まれる課題を検索する:

  description ~ "\"Please see screenshot\""

^top of fields | ^^top of topic

期限

特定の日付 (または日付範囲)、それよりも前、またはそれよりも後に期限切れとなった課題を検索します。期日は日付とのみ関連付けられます (時刻ではない)。

Note: this field does not support auto-complete.

構文

due

Alias (エイリアス):

dueDate

フィールド タイプ

DATE

サポートされる演算子

サポートされる関数

例

• 2010 年 12 月 31 日より前に期限切れとなった課題をすべて検索する:

  due < "2010/12/31"

• 2010 年 12 月 31 日以前に期限切れとなった課題をすべて検索する:

  due <= "2011/01/01"

• 期日が明日の課題をすべて検索する:

  due = "1d"

• 2011 年 1 月が期日の課題をすべて検索する:

  due >= "2011/01/01" and due <= "2011/01/31"

• 2011 年 1 月 15 日が期日の課題をすべて検索する:

  due = "2011/01/15"

^top of fields | ^^top of topic

環境

Search for issues where the Environment contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

構文

environment

フィールド タイプ

TEXT

サポートされる演算子

サポートされる関数

n/a

例

• Environment (環境) に "Third floor (3 階)" と一致するテキストが含まれる課題を検索する (例: 「あいまい」一致)

  environment ~ "Third floor"

• Environment (環境) に "Third floor (3 階)" との完全一致が含まれる課題を検索する:

  environment ~ "\"Third floor\""

^top of fields | ^^top of topic

フィルター

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).

注意:

• An Advanced Searching statement in your typed query will override an ORDER BY statement in the saved filter.
• 無限ループを発生させるフィルターを実行または保存することはできません (現在のフィルターを参照する保存済みフィルターを参照することはできません)。
• This field supports auto-complete.

  構文

  filter

  エイリアス:

  リクエスト

  savedFilter

  searchRequest

フィールド タイプ

フィルター

サポートされる演算子

サポートされる関数

n/a

例

• ユーザー jsmith に割り当てられた課題のフィルター "My Saved Filter (マイ保存済みフィルター)" (ID は 12000) の結果を検索する:

  filter = "My Saved Filter" and assignee = jsmith

  または

  filter = 12000 and assignee = jsmith

^top of fields | ^^top of topic

修正対象バージョン

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.

構文

fixVersion

フィールド タイプ

VERSION

サポートされる演算子

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.

サポートされる関数

例

• Fix Version (修正バージョン) が 3.14 または 4.2 の課題を検索する:

  fixVersion in ("3.14", "4.2")

  (Note that full-stops are reserved characters, so they need to be surrounded by quote marks.)

• Fix Version (修正バージョン) が "Little Ted" の課題を検索する:

  fixVersion = "Little Ted"

• Fix Version ID (修正バージョン ID) が 10001 の課題を検索する:

  fixVersion = 10001

^top of fields | ^^top of topic

課題キー

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.

構文

issueKey

エイリアス:

ID

課題

鍵 (キー)

フィールド タイプ

ISSUE

サポートされる演算子

サポートされる関数

When used with the IN or NOT IN operators, issueKey supports:

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

例

• キーが "ABC-123" の課題を検索する:

  issueKey = ABC-123

^top of fields | ^^top of topic

レベル

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.

構文

レベル

フィールド タイプ

SECURITY LEVEL

サポートされる演算子

サポートされる関数

n/a

例

• Security Level (セキュリティ レベル) が "Really High (非常に高い)" または "レベル1" の課題を検索する:

  level in ("Really High", level1)

• Security Level ID (セキュリティ レベル ID) が 123 の課題を検索する:

  level = 123

^top of fields | ^^top of topic

初期見積り

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).

"w"、"d"、"h"、"m" を使用して、週、日付、時間、分を指定します。

Note: this field does not support auto-complete.

構文

originalEstimate

Alias (エイリアス):

timeOriginalEstimate

フィールド タイプ

DURATION

サポートされる演算子

サポートされる関数

n/a

例

• Original Estimate (最初の予測) が 1 時間の課題を検索する:

  originalEstimate = 1h

• Original Estimate (最初の予測) が 2 日より多い課題を検索する:

  originalEstimate > 2d

^top of fields | ^^top of topic

親

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.

構文

parent

フィールド タイプ

ISSUE

サポートされる演算子

サポートされる関数

n/a

例

• "TEST-1234" を親に持つサブタスクを検索する:

  parent = TEST-1234

^top of fields | ^^top of topic

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.

構文

優先度

フィールド タイプ

PRIORITY

サポートされる演算子

サポートされる関数

n/a

例

• Priority (優先度) が "High (高)" の課題を検索する:

  priority = High

• Priority ID (優先度 ID) が 10000 の課題を検索する:

  priority = 10000

^top of fields | ^^top of topic

プロジェクト

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.

構文

プロジェクト

フィールド タイプ

PROJECT

サポートされる演算子

サポートされる関数

When used with the IN and NOT IN operators, project supports:

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

例

• "ABC Project" という名前のプロジェクトに所属する課題を検索する:

  project = "ABC Project"

• キーが "ABC" のプロジェクトに所属する課題を検索する:

  project = "ABC"

• ID が "1234" のプロジェクトに所属する課題を検索する:

  project = 1234

^top of fields | ^^top of topic

残余見積り

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).

"w"、"d"、"h"、"m" を使用して、週、日付、時間、分を指定します。

Note: this field does not support auto-complete.

構文

remainingEstimate

Alias (エイリアス):

timeEstimate

フィールド タイプ

DURATION

サポートされる演算子

サポートされる関数

n/a

例

• Remaining Estimate (残余予測) が 4 日より多い課題を検索する:

  remainingEstimate > 4h

^top of fields | ^^top of topic

報告者

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

検索条件にはユーザーのフルネーム、ID またはメールアドレスを使用できます。

Note: this field supports auto-complete.

構文

reporter

フィールド タイプ

USER

サポートされる演算子

サポートされる関数

例

• Jill Jones が作成した課題を検索する:

  reporter = "Jill Jones"

  または

  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.)

^top of fields | ^^top of topic

ソリューション

Search for issues that have a particular Resolution

検索条件には解決策名または解決策 ID (例: JIRA が解決策に自動的に割り当てる番号) を使用できます。

Note: this field supports auto-complete.

構文

resolution

フィールド タイプ

RESOLUTION

サポートされる演算子

サポートされる関数

n/a

例

• Resolution (解決策) が "Cannot Reproduce (再現不可)" または "Won't Fix (修正しない)" の課題を検索する:

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

• Resolution ID (解決策 ID) が 5 の課題を検索する:

  resolution = 5

• 解決策がない課題を検索する:

  resolution = unresolved

^top of fields | ^^top of topic

解決済み

Search for issues that were resolved on, before or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).

Note: this field does not support auto-complete.

構文

resolved

Alias (エイリアス):

resolutionDate

フィールド タイプ

DATE

サポートされる演算子

サポートされる関数

例

• Find all issues that were resolved before 31st December 2010:

  resolved <= "2010/12/31"

• 2010 年 12 月 31 日 の 2:00 pm より前に解決された課題をすべて検索する:

  resolved < "2010/12/31 14:00"

• 2010 年 12 月 31 日以前に解決された課題をすべて検索する:

  resolved <= "2011/01/01"

• 2011 年 1 月に解決された課題を検索する:

  resolved > "2011/01/01" and resolved < "2011/02/01"

• 2011 年 1 月 15 日に解決された課題を検索する:

  resolved > "2011/01/15" and resolved < "2011/01/16"

• 過去 1 時間以内に解決された課題を検索する:

  resolved > -1h

^top of fields | ^^top of topic

ステータス

Search for issues that have a particular Status.

検索条件にはステータス名またはステータス ID (例: JIRA がステータスに自動的に割り当てる番号) を使用できます。

Note: this field supports auto-complete.

構文

ステータス

フィールド タイプ

STATUS

サポートされる演算子

サポートされる関数

n/a

例

• Status (ステータス) が " Open (未処理)" の課題を検索する:

  status = Open

• Status ID (ステータス ID) が 1 の課題を検索する:

  status = 1

• 現在または過去のステータスが "Open (未処理)" である (であった) 課題を検索する:

  status WAS Open

^top of fields | ^^top of topic

要約

Search for issues where the Summary contains particular text.

JIRA text-search syntax can be used.

Note: this field does not support auto-complete.

構文

要約

フィールド タイプ

TEXT

サポートされる演算子

サポートされる関数

n/a

例

• Summary (概要) に "Error saving file (ファイルの保存エラー)" と一致するテキストが含まれる課題を検索する (例: 「あいまい」一致):

  summary ~ "Error saving file"

• Summary (概要) に "Error saving file (ファイルの保存エラー)" との完全一致が含まれる課題を検索する:

  summary ~ "\"Error saving file\""

^top of fields | ^^top of topic

Text

これは、次のすべてのテキスト フィールドを検索できる "マスター フィールド" です。

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

構文

text

フィールド タイプ

TEXT

サポートされる演算子

サポートされる関数

n/a

例

• テキスト フィールドが、"Fred" の単語と一致する課題を検索する:

  text ~ "Fred"

  または

  text ~ Fred

• テキスト フィールドに "full screen (フルスクリーン)" と完全一致が含まれる課題をすべて検索する:

  text ~ "\"full screen\""

^top of fields | ^^top of topic

タイプ

Search for issues that have a particular Issue Type.

検索は課題タイプ名または課題タイプ ID (例: JIRA が課題タイプに自動的に割り当てる番号) のいずれかに基づいて行われます。

Note: this field supports auto-complete.

構文

type

Alias (エイリアス):

issueType

フィールド タイプ

ISSUE_TYPE

サポートされる演算子

サポートされる関数

n/a

例

• Issue Type (課題タイプ) が "Bug (バグ)" の課題を検索する:

  type = Bug

• Issue Type (課題タイプ) が "Bug (バグ)" または "Improvement (改善)" の課題を検索する:

  issueType in (Bug,Improvement)

• Issue Type ID (課題タイプ ID) が 2 の課題を検索する:

  issueType = 2

^top of fields | ^^top of topic

消費時間

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).

"w"、"d"、"h"、"m" を使用して、週、日付、時間、分を指定します。

Note: this field does not support auto-complete.

構文

timeSpent

フィールド タイプ

DURATION

サポートされる演算子

サポートされる関数

n/a

例

• Time Spent (所要時間) が 5 日より多い課題を検索する:

  timeSpent > 5d

^top of fields | ^^top of topic

更新日

Search for issues that were last updated on, before or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results will be relative to your configured time zone (which is by default the JIRA server's time zone).

Note: this field does not support auto-complete.

構文

updated

Alias (エイリアス):

updatedDate

フィールド タイプ

DATE

サポートされる演算子

サポートされる関数

例

• 最後に更新されたのが 2010 年 12 月 12 日より前の課題を検索する:

  updated < "2010/12/12"

• 最後に更新されたのが 2010 年 12 月 12 日より前の課題を検索する:

  updated < "2010/12/13"

• 2010 年 12 月 31 日 の 2:00 pm より前に更新された課題をすべて検索する:

  updated < "2010/12/31 14:00"

• 最後に更新されたのが 2 週間より前の課題を検索する:

  updated < "-2w"

• 最後に更新されたのが 2011 年 1 月 15 日の課題を検索する:

  updated > "2011/01/15" and updated < "2011/01/16"

• 最後に更新されたのが 2011 年 1 月の課題を検索する:

  updated > "20011/01/01" and updated < "2011/02/01"

^top of fields | ^^top of topic

投票者

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.

構文

voter

フィールド タイプ

USER

サポートされる演算子

サポートされる関数

例

• 自分が投票した課題を検索する:

  voter = currentUser()

• ユーザー "jsmith" が投票した課題を検索する:

  voter = "jsmith"

• グループ "jira-developers" のメンバーが投票した課題を検索する:

  voter in membersOf("jira-developers")

^top of fields | ^^top of topic

投票数

Search for issues with a specified number of votes.

Note: this field does not support auto-complete.

構文

votes

フィールド タイプ

NUMBER

サポートされる演算子

サポートされる関数

n/a

例

• 12 票以上の課題をすべて検索する:

  votes >= 12

^top of fields | ^^top of topic

ウォッチャー

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.

構文

watcher

フィールド タイプ

USER

サポートされる演算子

サポートされる関数

例

• 自分がウォッチしている課題を検索する:

  watcher = currentUser()

• ユーザー "jsmith" がウォッチしている課題を検索する:

  watcher = "jsmith"

• グループ "jira-developers" がウォッチしている課題を検索する:

  watcher in membersOf("jira-developers")

^top of fields | ^^top of topic

ウォッチャー

Search for issues with a specified number of watchers.

Note: this field does not support auto-complete.

構文

watchers

フィールド タイプ

NUMBER

サポートされる演算子

サポートされる関数

n/a

例

• 3 人以上にウォッチされている課題をすべて検索する:

  watchers > 3

^top of fields | ^^top of topic

Work Ratio (作業率)

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

Work Ratio (作業率) が特定の値の課題を検索します。

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

Note: this field does not support auto-complete.

構文

workRatio

フィールド タイプ

NUMBER

サポートされる演算子

サポートされる関数

n/a

例

• 所要時間が Original Estimate (最初の予測) の 75 % より多い課題を検索する:

  workRatio > 75

^top of fields | ^^top of topic

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.

構文

cascadeOption(parentOption)

または

cascadeOption(parentOption,childOption)

Supported Fields

• custom fields of type 'Cascading Select'

サポートされる演算子

例

• 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)

^top of functions | ^^top of topic

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.

構文

componentsLeadByUser()

または

componentsLeadByUser(username)

Supported Fields

• コンポーネント

サポートされる演算子

例

• 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

^top of functions | ^^top of topic

currentLogin()

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

構文

currentLogin()

Supported Fields

サポートされる演算子

例

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

  created > currentLogin()

^top of functions | ^^top of topic

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.

構文

currentUser()

Supported Fields

サポートされる演算子

例

• Find issues that are assigned to me:

  assignee = currentUser()

• 自分が報告したが自分に割り当てられていない課題を検索:

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

^top of functions | ^^top of topic

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.

Note that the "earliest" is determined by the ordering assigned to the versions, not by actual Version Due Dates.

構文

earliestUnreleasedVersion(project)

Supported Fields

サポートされる演算子

例

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

  fixVersion = earliestUnreleasedVersion(ABC)

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

  affectedVersion = earliestUnreleasedVersion(ABC) or fixVersion = earliestUnreleasedVersion(ABC)

^top of functions | ^^top of topic

endOfDay()

Perform searches based on the end of the current day. See also endOfWeek, endOfMonth and endOfYear; and startOfDay, startOfWeek, startOfMonth and startOfYear.

構文

endOfDay()

または

endOfDay("inc")

where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)

• If the time unit qualifier is omitted it defaults to the natural period of the function, e.g. endOfDay("+1") is the same as endOfDay("+1d").
• If the plus/minus (+/-) sign is omitted, plus is assumed.

Supported Fields

サポートされる演算子

例

• Find issues due by the end of today:

  due < endOfDay()

• Find issues due by the end of tomorrow:

  due < endOfDay("+1")

^top of functions | ^^top of topic

endOfMonth()

Perform searches based on the end of the current month. See also endOfDay, endOfWeek and endOfYear; and startOfDay, startOfWeek, startOfMonth and startOfYear.

構文

endOfMonth()

または

endOfMonth("inc")

where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)

• If the time unit qualifier is omitted it defaults to the natural period of the function, e.g. endOfMonth("+1") is the same as endOfMonth("+1M").
• If the plus/minus (+/-) sign is omitted, plus is assumed.

Supported Fields

サポートされる演算子

例

• Find issues due by the end of this month:

  due < endOfMonth()

• Find issues due by the end of next month:

  due endOfMonth("+1")

• Find issues due by the 15th of next month:

  due endOfMonth("+15d")

^top of functions | ^^top of topic

endOfWeek()

Perform searches based on the end of the current week. See also endOfDay, endOfMonth and endOfYear; and 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.

構文

endOfWeek()

または

endOfWeek("inc")

where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)

• If the time unit qualifier is omitted it defaults to the natural period of the function, e.g. endOfWeek("+1") is the same as endofWeek("+1w").
• If the plus/minus (+/-) sign is omitted, plus is assumed.

Supported Fields

サポートされる演算子

例

• Find issues due by the end of this week:

  due < endOfWeek()

• Find issues due by the end of next week:

  due < endOfWeek("+1")

^top of functions | ^^top of topic

endOfYear()

Perform searches based on the end of the current year. See also startOfDay, startOfWeek and startOfMonth; and endOfDay, endOfWeek, endOfMonth and endOfYear.

startOfYear()

または

startOfYear("inc")

where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)

• If the time unit qualifier is omitted it defaults to the natural period of the function, e.g. endOfYear("+1") is the same as endofYear("+1y").
• If the plus/minus (+/-) sign is omitted, plus is assumed.

Supported Fields

サポートされる演算子

例

• Find issues due by the end of this year:

  due < endOfYear()

• Find issues due by the end of March next year:

  due < endOfYear("+3M")

^top of functions | ^^top of topic

issueHistory()

最近閲覧した課題、つまり [課題] ドロップダウン メニューの [最近表示した課題] セクションにある課題を検索します。

注意:

• issueHistory() returns up to 50 issues, whereas the 'Recent Issues' drop-down returns only 5.
• JIRA にログインしていない場合、現在利用しているブラウザのセッションから取得した課題だけが含まれます。

構文

issueHistory()

Supported Fields

• 課題

サポートされる演算子

例

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

  issue in issueHistory() AND assignee = currentUser()

^top of functions | ^^top of topic

lastLogin()

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

構文

currentLogin()

Supported Fields

サポートされる演算子

例

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

  created > lastLogin()

^top of functions | ^^top of topic

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().

Note that the "latest" is determined by the ordering assigned to the versions, not by actual Version Due Dates.

構文

latestReleasedVersion(project)

Supported Fields

サポートされる演算子

例

• Find issues whose FixVersionis the latest released version of the ABC project:

  fixVersion = latestReleasedVersion(ABC)

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

  affectedVersion = latestReleasedVersion(ABC) or fixVersion = latestReleasedVersion(ABC)

^top of functions | ^^top of topic

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.

構文

linkedIssues(issueKey)

または

linkedIssues(issueKey,linkType)

Supported Fields

• 課題

サポートされる演算子

例

• 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")

^top of functions | ^^top of topic

membersOf()

特定のグループのメンバーに基づく検索を実施します。

構文

membersOf（グループ）

Supported Fields

サポートされる演算子

例

• 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)

^top of functions | ^^top of topic

now()

現在の時刻に基づいた検索を行います。

構文

now()

Supported Fields

サポートされる演算子

例

• Find issues that are overdue:

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

^top of functions | ^^top of topic

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.

構文

projectsLeadByUser()

または

projectsLeadByUser(username)

Supported Fields

• プロジェクト

サポートされる演算子

例

• 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

^top of functions | ^^top of topic

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 that this function is only available if you are logged in to JIRA.

構文

projectsWhereUserHasPermission(permission)

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

Supported Fields

• プロジェクト

サポートされる演算子

例

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

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

^top of functions | ^^top of topic

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.

構文

projectsWhereUserHasRole(rolename)

Supported Fields

• プロジェクト

サポートされる演算子

例

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

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

^top of functions | ^^top of topic

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().

構文

releasedVersions()

または

releasedVersions(project)

Supported Fields

サポートされる演算子

例

• Find issues whose FixVersionis 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)

  または

  fixVersion in releasedVersions(ABC)

^top of functions | ^^top of topic

standardIssueTypes()

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

See also subtaskIssueTypes().

構文

standardIssueTypes()

Supported Fields

• タイプ

サポートされる演算子

例

• 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()

^top of functions | ^^top of topic

startOfDay()

Perform searches based on the start of the current day. See also startOfWeek, startOfMonth and startOfYear; and endOfDay, endOfWeek, endOfMonth and endOfYear.

構文

startOfDay()

または

startOfDay("inc")

where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)

• If the time unit qualifier is omitted it defaults to the natural period of the function, e.g. startOfDay("+1") is the same as startofDay("+1d").
• If the plus/minus (+/-) sign is omitted, plus is assumed.

Supported Fields

サポートされる演算子

例

• Find new issues created since the start of today:

  created > startOfDay()

• Find new issues created since the start of yesterday:

  created > startOfDay("-1")

• Find new issues created in the last three days:

  created > startOfDay("-3d")

^top of functions | ^^top of topic

startOfMonth()

Perform searches based on the start of the current month. See also startOfDay, startOfWeek and startOfYear; and endOfDay, endOfWeek, endOfMonth and endOfYear.

構文

startOfMonth()

または

startOfMonth("inc")

where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)

• If the time unit qualifier is omitted it defaults to the natural period of the function, e.g. startOfMonth("+1") is the same as startofMonth("+1M").
• If the plus/minus (+/-) sign is omitted, plus is assumed.

Supported Fields

サポートされる演算子

例

• Find new issues since the start of this month:

  created > startOfMonth()

• Find new issues since the start of last month:

  created > startOfMonth("-1")

• Find new issues since the 15th of this month:

  created > startOfMonth("+14d")

^top of functions | ^^top of topic

startOfWeek()

Perform searches based on the start of the current week. See also startOfDay, startOfMonth and startOfYear; and 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.

構文

startOfWeek()

または

startOfWeek("inc")

where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)

• If the time unit qualifier is omitted it defaults to the natural period of the function, e.g. startOfWeek("+1") is the same as startofWeek("+1w").
• If the plus/minus (+/-) sign is omitted, plus is assumed.

Supported Fields

サポートされる演算子

例

• Find new issues since the start of this week:

  created > startOfWeek()

• Find new issues since the start of last week:

  created > startOfWeek("-1")

^top of functions | ^^top of topic

startOfYear()

Perform searches based on the start of the current year. See also startOfDay, startOfWeek and startOfMonth; and endOfDay, endOfWeek, endOfMonth and endOfYear.

startOfYear()

または

startOfYear("inc")

where inc is an optional increment of (+/-)nn(y|M|w|d|h|m)

• If the time unit qualifier is omitted it defaults to the natural period of the function, e.g. startOfYear("+1") is the same as startofYear("+1y").
• If the plus/minus (+/-) sign is omitted, plus is assumed.

Supported Fields

サポートされる演算子

例

• Find new issues since the start of this year:

  created > startOfYear()

• Find new issues since the start of last year:

  created > startOfYear("-1")

^top of functions | ^^top of topic

subtaskIssueTypes()

Perform searches based on issues which are sub-tasks.

See also standardIssueTypes().

構文

subtaskIssueTypes()

Supported Fields

• タイプ

サポートされる演算子

例

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

  issuetype in subtaskIssueTypes()

^top of functions | ^^top of topic

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().

構文

unreleasedVersions()

または

unreleasedVersions(project)

Supported Fields

サポートされる演算子

例

• Find issues whose FixVersionis 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)

  または

  fixVersion in unreleasedVersions(ABC)

^top of functions | ^^top of topic

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.

構文

votedIssues()

Supported Fields

• 課題

サポートされる演算子

例

• Find issues that you have voted for:

  issue in votedIssues()

^top of functions | ^^top of topic

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.

構文

watchedIssues()

Supported Fields

• 課題

サポートされる演算子

例

• Find issues that you are watching:

  issue in watchedIssues()

Supported Fields

• 課題

サポートされる演算子

例

• Find issues that you have recently viewed:

  issue in issueHistory()

^top of functions | ^^top of topic

(status=resolved AND project=SysAdmin) OR assignee=bobsmith

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.:

version = "[example]"

version = "4.2"

summary ~ "\\[example\\]"

summary ~ "4.2"