高度な検索 - フィールド参照
A field in JQL is a word that represents a JIRA field (or a custom field that has already been defined in JIRA). In a clause, a field is followed by an operator, which in turn is followed by one or more values (or functions). The operator compares the value of the field with one or more values or functions on the right, such that only true results are retrieved by the clause.
フィールド一覧:
対象バージョン
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).
バージョン名で検索するよりも、バージョン ID で検索する方が安全です。
Different projects may have versions with the same name, so searching by version name may return issues from multiple projects. It is also possible for your JIRA administrator to change the name of a version, which could break any saved filters which rely on that name. Version IDs, however, are unique and cannot be changed.
Note: this field supports auto-complete.
構文
affectedVersion
フィールド タイプ
VERSION
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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.
サポートされる関数
- releasedVersions()
- latestReleasedVersion()
- unreleasedVersions()
- earliestUnreleasedVersion()
例
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.
構文
assignee
フィールド タイプ
USER
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
例
John Smith に割り当てられた課題を検索する:
assignee = "John Smith"または
assignee = jsmithJohn Smith に現在割り当てられている、または過去に割り当てられていた課題を検索する:
assignee WAS "John Smith"または
assignee WAS jsmithFind 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
添付ファイル
添付ファイルがある、または添付ファイルがない課題を検索します。このフィールドには EMPTY または IS NOT EMPTY 演算子のみを使用できます。
Note: this field supports auto-complete.
構文
attachments
フィールド タイプ
ATTACHMENT
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
なし
例
添付ファイルがある課題を検索する
attachments IS NOT EMPTY添付ファイルがない課題を検索する
attachments IS EMPTY
^top of fields | ^^top of topic
カテゴリ
特定のカテゴリー内のプロジェクトに所属する課題を検索します。
Note: this field supports auto-complete.
構文
category
フィールド タイプ
CATEGORY
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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).
コンポーネント名で検索するよりも、コンポーネント ID で検索する方が安全です。
Different projects may have components with the same name, so searching by component name may return issues from multiple projects. It is also possible for your JIRA administrator to change the name of a component, which could break any saved filters which rely on that name. Component IDs, however, are unique and cannot be changed.
Note: this field supports auto-complete.
構文
component
フィールド タイプ
COMPONENT
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
When used with the IN and NOT IN operators, component supports:
例
"Comp1" または "Comp2" コンポーネント内の課題を検索する:
component in (Comp1, Comp2)"Comp1" および "Comp2" コンポーネント内の課題を検索する:
component in (Comp1) and component in (Comp2)または
component = Comp1 and component = Comp2ID が 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 00:00 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).
"yyyy/MM/dd HH:mm"
"yyyy-MM-dd HH:mm"
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w" (weeks), "d" (days), "h" (hours) or "m" (minutes) to specify a date relative to the current time. The default is "m" (minutes). Be sure to use quote-marks ("); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).
Note: this field does not support auto-complete.
構文
created
Alias (エイリアス):
createdDate
フィールド タイプ
DATE
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
例
2010 年 12 月 12 日の真夜中 00:00 より前に作成された課題をすべて検索する:
created < "2010/12/12"2010 年 12 月 12 日以前 (ただし 2010 年 12 月 13 日以外) に作成された課題をすべて検索する:
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
作成者
特定のユーザー以外が作成した課題を検索する:
検索条件にはユーザーのフルネーム、ID またはメールアドレスを使用できます。
Note: this field supports auto-complete.
構文
creator
フィールド タイプ
USER
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
例
Jill Jones が作成した課題を検索する:
creator = "Jill Jones"または
creator = jjonesSearch for issues that were created by the user with email address "bob@mycompany.com":
creator = "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
カスタム フィールド
Only applicable if your JIRA administrator has created one or more Custom Fields.
特定のカスタム フィールドに特定の値が入力された課題を検索します。
検索条件にはカスタム フィールド名またはカスタム フィールド ID (例: JIRA がカスタム フィールドに自動的に割り当てた番号) を使用できます。
カスタム フィールド名で検索するよりも、カスタム フィールド ID で検索する方が安全です。
It is possible for a Custom Field to have the same name as a built-in JIRA system field, in which case JIRA will search on the system field (not your custom field). It is also possible for your JIRA administrator to change the name of a Custom Field, which could break any saved filters which rely on that name. Custom Field IDs, however, are unique and cannot be changed.
注意:
- 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, 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:
- 数字および日付/ 時刻フィールド:
=
!=
~
!~
>
>=
<
<=
IS
IS NOT
IN
NOT IN
WAS
WAS IN
WAS NOT
WAS NOT IN
CHANGED - ピッカー、選択、チェックボックス、ラジオ ボタン フィールド:
=
!=
~
!~
>
>=
<
<=
IS
IS NOT
IN
NOT IN
WAS
WAS IN
WAS NOT
WAS NOT IN
CHANGED - テキスト フィールド:
=
!=
~
!~
>
>=
<
<=
IS
IS NOT
IN
NOT IN
WAS
WAS IN
WAS NOT
WAS NOT IN
CHANGED
サポートされる関数
Different types of Custom Fields support different functions. For the default Custom Field Types, the following functions are supported:
- Date/time fields: EQUALS、NOT EQUALS、GREATER THAN、GREATER THAN EQUALS、LESS THAN、 LESS THAN EQUALS 演算子と共に使用する場合、このフィールドは以下をサポートします:
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
- 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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
n/a
例
Description (説明) に "Please see screenshot (スクリーンショットを参照)" と一致するテキストが含まれる課題を検索する (例: 「あいまい」一致):
description ~ "Please see screenshot"Description (説明) に "Please see screenshot (スクリーンショットを参照)" との完全一致が含まれる課題を検索する:
description ~ "\"Please see screenshot\""
^top of fields | ^^top of topic
期限
特定の日付 (または日付範囲)、それよりも前、またはそれよりも後に期限切れとなった課題を検索します。期日は日付とのみ関連付けられます (時刻ではない)。
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w" (weeks) or "d" (days) to specify a date relative to the current date. Be sure to use quote-marks (").
Note: this field does not support auto-complete.
構文
due
Alias (エイリアス):
dueDate
フィールド タイプ
DATE
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
例
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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
n/a
例
Environment (環境) に "Third floor (3 階)" と一致するテキストが含まれる課題を検索する (例: 「あいまい」一致)
environment ~ "Third floor"Environment (環境) に "Third floor (3 階)" との完全一致が含まれる課題を検索する:
environment ~ "\"Third floor\""
^top of fields | ^^top of topic
Epic Link (エピック リンク)
Only available if you are using JIRA Agile 6.1.2 or later.
Search for issues that belong to a particular Epic in JIRA Agile. The search is based on either the epic's Name, Issue Key or Issue ID (i.e. the number that JIRA automatically allocates to an Issue).
Note: this field does not support auto-complete.
構文
"epic link"
フィールド タイプ
エピック リンク リレーションシップ (JIRA Agile によって作成されたカスタムのタイプ)。
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
When used with the IN or NOT IN operators, epic link supports:
- issueHistory()
- linkedIssues()
- votedIssues()
- watchedIssues()
例
エピック "Jupiter" (課題キー ANERDS-317) に所属する課題を検索する:
"epic link" = ANERDS-317または
"epic link" = Jupiter
^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).
フィルター名で検索するよりも、フィルター ID で検索する方が安全です。
フィルター名が変更されて保存済みフィルターが壊れ、名前で別のフィルタが呼び出されてしまう可能性があります。ただし、フィルター ID は一意であり、変更できません。
注意:
- An Advanced Searching - Fields Reference statement in your typed query will override an ORDER BY statement in the saved filter.
- 無限ループを発生させるフィルターを実行または保存することはできません (現在のフィルターを参照する保存済みフィルターを参照することはできません)。
- This field supports auto-complete.
構文
filterエイリアス:
requestsavedFiltersearchRequest
フィールド タイプ
フィルター
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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).
バージョン名で検索するよりも、バージョン ID で検索する方が安全です。
Different projects may have versions with the same name, so searching by version name may return issues from multiple projects. It is also possible for your JIRA administrator to change the name of a version, which could break any saved filters that rely on that name. Version IDs, however, are unique and cannot be changed.
Note: this field supports auto-complete.
構文
fixVersion
フィールド タイプ
VERSION
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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.
サポートされる関数
- releasedVersions()
- latestReleasedVersion()
- unreleasedVersions()
- earliestUnreleasedVersion()
例
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
key
フィールド タイプ
ISSUE
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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
LastViewed (最終閲覧日)
Search for issues that were last viewed on, before or after a particular date (or date range). Note that if a time-component is not specified, midnight 00:00 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).
"yyyy/MM/dd HH:mm"
"yyyy-MM-dd HH:mm"
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w" (weeks), "d" (days), "h" (hours) or "m" (minutes) to specify a date relative to the current time. The default is "m" (minutes). Be sure to use quote-marks ("); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).
Note: this field does not support auto-complete.
構文
lastViewed
フィールド タイプ
DATE
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
例
最後に閲覧されたのが 2010 年 12 月 12 日より前の課題をすべて検索する:
lastViewed < "2010/12/12"Find all issues last viewed on or before 12th December 2010 (but not 13th December 2010):
lastViewed <= "2010/12/13"最後に閲覧されたのが 2010 年 12 月 12 日 2:00pm より前の課題をすべて検索する:
lastViewed > "2010/12/12" and created < "2010/12/12 14:00"最後に閲覧されたのが 1 日以内の課題を検索する:
lastViewed > "-1d"最後に閲覧されたのが 2011 年 1 月の課題を検索する:
lastViewed > "2011/01/01" and created < "2011/02/01"最後に閲覧されたのが 2011 年 1 月 15 日の課題を検索する:
lastViewed > "2011/01/15" and created < "2011/01/16"
^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).
セキュリティ レベル名で検索するよりも、セキュリティ レベル ID で検索する方が安全です。
It is possible for your JIRA administrator to change the name of a Security Level, which could break any saved filter which rely on that name. Security Level IDs, however, are unique and cannot be changed.
Note: this field supports auto-complete.
構文
level
フィールド タイプ
SECURITY LEVEL
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
n/a
例
Original Estimate (最初の予測) が 1 時間の課題を検索する:
originalEstimate = 1hOriginal 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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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).
優先度名で検索するよりも、優先度 ID で検索する方が安全です。
It is possible for your JIRA administrator to change the name of a Priority, which could break any saved filter which rely on that name. Priority IDs, however, are unique and cannot be changed.
Note: this field supports auto-complete.
構文
priority
フィールド タイプ
PRIORITY
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
n/a
例
Priority (優先度) が "High (高)" の課題を検索する:
priority = HighPriority 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). In the rare case where there is a project whose project key is the same as another project's name, then the project key takes preference and hides results from the second project.
Note: this field supports auto-complete.
構文
project
フィールド タイプ
PROJECT
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
n/a
例
Remaining Estimate (残余予測) が 4 日より多い課題を検索する:
remainingEstimate > 4h
^top of fields | ^^top of topic
報告者
特定のユーザーによって報告された課題を検索します。このユーザーが作成者と同じ場合もありますが、明確ではありません。
検索条件にはユーザーのフルネーム、ID またはメールアドレスを使用できます。
Note: this field supports auto-complete.
構文
reporter
フィールド タイプ
USER
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
例
Jill Jones が報告した課題を検索する:
reporter = "Jill Jones"または
reporter = jjonesSearch for issues that were reported by the user with email address "bob@mycompany.com":
reporter = "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 が解決策に自動的に割り当てる番号) を使用できます。
解決策名で検索するよりも、解決策 ID で検索する方が安全です。
It is possible for your JIRA administrator to change the name of a Resolution, which could break any saved filter which rely on that name. Resolution IDs, however, are unique and cannot be changed.
Note: this field supports auto-complete.
構文
resolution
フィールド タイプ
RESOLUTION
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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 00:00 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).
"yyyy/MM/dd HH:mm"
"yyyy-MM-dd HH:mm"
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w" (weeks), "d" (days), "h" (hours) or "m" (minutes) to specify a date relative to the current time. The default is "m" (minutes). Be sure to use quote-marks ("); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).
Note: this field does not support auto-complete.
構文
resolved
Alias (エイリアス):
resolutionDate
フィールド タイプ
DATE
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
例
Find all issues that were resolved before 31st December 2010 (but not on 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
Sprint
Only available if you are using JIRA Agile.
Search for issues that are assigned to a particular sprint in JIRA Agile. This works for active sprints and future sprints. The search is based on either the sprint name or the sprint ID (i.e. the number that JIRA automatically allocates to a sprint).
構文
sprint
似た名前、あるいは同じ名前の複数のスプリントがある場合、スプリント名またはスプリント名の一部を使用して検索できます。一致候補はオートコンプリート ドロップダウンに表示され、表示されるスプリントの日付でスプリントを見分けることができます (括弧内にスプリント ID も表示されます)。
フィールド タイプ
数値
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- openSprints()
- closedSprints()
例
スプリント 999 に所属する課題を検索する:
sprint = 999スプリント "February 1" に所属する課題を検索する:
sprint = "February 1""February 1"、"February 2" または "February 3" のいずれかに所属する課題を検索する:
sprint in ("February 1","February 2","February 3")スプリントに割り当てられた課題を検索する:
sprint is not empty
^top of fields | ^^top of topic
ステータス
Search for issues that have a particular Status.
検索条件にはステータス名またはステータス ID (例: JIRA がステータスに自動的に割り当てる番号) を使用できます。
ステータス名で検索するよりも、ステータス ID で検索する方が安全です。
It is possible for your JIRA administrator to change the name of a Status, which could break any saved filter which rely on that name. Status IDs, however, are unique and cannot be changed.
Please note, though, that the
WAS
,
WAS_NOT
,
WAS_IN
and
WAS_NOT_IN
operators can only be used with the name (not the ID).
Note: this field supports auto-complete.
構文
status
フィールド タイプ
STATUS
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
n/a
例
Status (ステータス) が " Open (未処理)" の課題を検索する:
status = OpenStatus 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.
構文
summary
フィールド タイプ
TEXT
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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
これは、次のすべてのテキスト フィールドを検索できる "マスター フィールド" です。
- 要約
- 説明
- 環境
- コメント
- custom fields which use the "Free Text Searcher"; this includes custom fields of the following built-in Custom Field Types
- フリー テキスト フィールド (無制限のテキスト)
- テキスト フィールド (255 文字までのテキスト)
- 読み取り専用テキスト フィールド
The JQL field "text" as in text ~ "some words" searches an issue's Summary, Description, Environment, Comments. It also searches all text custom fields. If you have many text custom fields you can improve performance of your queries by searching on specific fields, e.g. Summary ~ "some words" OR Description ~ "some words"
メモ:
- The
textmaster-field can only be used with the CONTAINS operator ("~"). - JIRA text-search syntax can be used with these fields.
構文
text
フィールド タイプ
TEXT
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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 が課題タイプに自動的に割り当てる番号) のいずれかに基づいて行われます。
タイプ名で検索するよりも、タイプ ID で検索する方が安全です。
It is possible for your JIRA administrator to change the name of a Type, which could break any saved filter which rely on that name. Type IDs, however, are unique and cannot be changed.
Note: this field supports auto-complete.
構文
type
Alias (エイリアス):
issueType
フィールド タイプ
ISSUE_TYPE
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
n/a
例
Issue Type (課題タイプ) が "Bug (バグ)" の課題を検索する:
type = BugIssue 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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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 00:00 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).
"yyyy/MM/dd HH:mm"
"yyyy-MM-dd HH:mm"
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w" (weeks), "d" (days), "h" (hours) or "m" (minutes) to specify a date relative to the current time. The default is "m" (minutes). Be sure to use quote-marks ("); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).
Note: this field does not support auto-complete.
構文
updated
Alias (エイリアス):
updatedDate
フィールド タイプ
DATE
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
例
最後に更新されたのが 2010 年 12 月 12 日より前の課題を検索する:
updated < "2010/12/12"Find issues that were last updated on or before 12th December 2010 (but not 13th December 2010):
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 > "2011/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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
例
自分が投票した課題を検索する:
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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
例
自分がウォッチしている課題を検索する:
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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
n/a
例
3 人以上にウォッチされている課題をすべて検索する:
watchers > 3
^top of fields | ^^top of topic
Work Log Author
Only available if time-tracking has been enabled by your JIRA administrator.
Search for issues a particular user has logged work against. You can search by the user's Full Name, ID, or Email Address. Note that you can only find issues for which you have "Time Tracking" permissions, unless you are searching for issues that you've logged work against.
Note: this field supports auto-complete.
構文
worklogAuthor
フィールド タイプ
USER
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- membersOf()
When used with the EQUALS and NOT EQUALS operators, this field supports:
- currentUser()
例
Search for issues that you've logged work against:
worklogAuthor = currentUser()Search for issues that the user "jsmith" has logged work against:
worklogAuthor = "jsmith"Search for issues that a member of the group "jira-developers" has logged work against:
worklogAuthor in membersOf("jira-developers")
^top of fields | ^^top of topic
Work Log Comment
Only available if time-tracking has been enabled by your JIRA administrator.
Search for issues that have a Comment in a work log entry which contains particular text.
JIRA text-search syntax can be used.
Note: this field does not support auto-complete.
構文
worklogComment
フィールド タイプ
TEXT
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
n/a
例
Find issues where a Comment in a work log entry contains text that matches "test sessions" (i.e. a "fuzzy" match):
comment ~ "test sessions"Find issues where a Comment contains the exact phrase "test sessions":
comment ~ "\"test sessions\""
^top of fields | ^^top of topic
Work Log Date
Only available if time-tracking has been enabled by your JIRA administrator.
Search for issues that have comments in work log entries that were created on, before, or after a particular date (or date range). Note that if a time-component is not specified, midnight 00:00 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).
"yyyy/MM/dd HH:mm"
"yyyy-MM-dd HH:mm"
"yyyy/MM/dd"
"yyyy-MM-dd"
Or use "w" (weeks), "d" (days), "h" (hours) or "m" (minutes) to specify a date relative to the current time. The default is "m" (minutes). Be sure to use quote-marks ("); if you omit the quote-marks, the number you supply will be interpreted as milliseconds after epoch (1970-1-1).
Note: this field does not support auto-complete.
構文
worklogDate
フィールド タイプ
DATE
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
- currentLogin()
- lastLogin()
- now()
- startOfDay()
- startOfWeek()
- startOfMonth()
- startOfYear()
- endOfDay()
- endOfWeek()
- endOfMonth()
- endOfYear()
例
Find issues that have comments in work log entries created before midnight 00:00 12th December 2010:
worklogDate < "2010/12/12"Find issues that have comments in work log entries created on or before 12th December 2010 (but not 13th December 2010):
worklogDate <= "2010/12/13"Find issues that have comments in work log entries created on 12th December 2010 before 2:00pm:
worklogDate > "2010/12/12" and worklogDate < "2010/12/12 14:00"Find issues that have comments in work log entries created less than one day ago:
worklogDate > "-1d"Find issues that have comments in work log entries created in January 2011:
worklogDate > "2011/01/01" worklogDate < "2011/02/01"Find issues that have comments in work log entries created on 15 January 2011:
worklogDate > "2011/01/15" and worklogDate < "2011/01/16"
^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
サポートされる演算子
= | != | ~ | !~ | > | >= | < | <= | IS | IS NOT | IN | NOT IN | WAS | WAS IN | WAS NOT | WAS NOT IN | CHANGED |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
サポートされる関数
n/a
例
所要時間が Original Estimate (最初の予測) の 75 % より多い課題を検索する:
workRatio > 75