詳細検索

The instructions on this page describe how to define and execute a search using the advanced search. You can also define and execute a search using the quick search or using basic searching.

高度な検索とは

An advanced search allows you to use structured queries to search for JIRA issues. Your search results will be displayed in the Issue Navigator, where you can export them to MS Excel and many other formats. You can also save and subscribe to your advanced searches if you wish.

高度な検索を実行するときには、JIRA クエリ言語 (JQL) を使用します。

A simple query in JQL (also known as a 'clause') consists of a field, followed by an operator, followed by one or more values or functions. For example, the following simple query will find all issues in the "TEST" project:

project = "TEST"

(This example uses the Project field, the EQUALS operator, and the value "TEST".)

Be aware that it is not possible to compare two fields.

(info) JQL gives you some SQL-like syntax, such as the ORDER BY SQL keyword and ISNULL() SQL function (i.e. the NULL keyword in JQL). However, JQL is not a database query language. For example, JQL does not have a SELECT statement.

高度な検索を実行するには

  1. Choose Issues > Search for Issues. The issue navigator will be displayed.
    • 既存の検索条件がある場合は、New filter (新しいフィルター)ボタンをクリックして検索条件をリセットします。
    • Advanced (詳細設定)リンクが表示されたら、クリックして高度な検索に切り替えます。
  2. Type your query using the fields, operators and field values or functions.
  3. Search (検索) ボタンをクリックしてクエリを実行します。

Performing Text Searches

You can use Lucene's text-searching features when performing searches on the following fields, using the CONTAINS operator:

  • 要約
  • 説明
  • 環境
  • コメント
  • 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"

For details, please see the page on Performing Text Searches.

自動入力を使用する

クエリを入力すると、JIRA はコンテキストを認識し、次のように「オートコンプリート」候補のリストを表示します:

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.

注意:

  • If no auto-complete suggestions are offered, your administrator may have disabled the "JQL Auto-complete" feature for your JIRA instance.
  • If you prefer not to be offered auto-complete suggestions, click the "Turn off auto-complete" link below the "Query" box.

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

「高度な」検索と「簡易」検索の切り替え

In general, a query created using 'Simple Search' will be able to be translated to 'Advanced Search' (i.e. JQL), and back again.

ただし、「高度な検索」を使用して作成されたクエリを「簡易検索」に変換することはできません。特に次のような場合は変換できません。

  • the query contains an OR operator (note you can have an IN operator and it will be translated, e.g. project in (A, B))
    • i.e. even though this query: (project = JRA OR project = CONF) is equivalent to this query: (project in (JRA, CONF)), only the second query will be translated.
  • NOT 演算子を含むクエリ
  • EMPTY 演算子を含むクエリ
  • 比較演算子 (!=、IS、IS NOT、>、>=、<、<=) を含むクエリ
  • the query specifies a field and value that is related to a project (e.g. version, component, custom fields) and the project is not explicitly included in the query (e.g. fixVersion = "4.0", without the AND project=JRA). This is especially tricky with custom fields since they can be configured on a Project/Issue Type basis. The general rule of thumb is that if the query cannot be created in the 'Simple Search' form, then if it is created using 'Advanced Search' it will not be able to be translated to 'Simple Search'.

 

演算子の優先順位の設定

You can use parentheses in complex JQL statements to enforce the precedence of operators.

例えば、SysAdmin プロジェクトの解決済みの課題すべてと、システム管理者 (bobsmith) に現状、割り当てられているすべての課題を検索したい場合、 括弧を使用してクエリ内のブーリアン演算子の優先順位を変更できます。
例:

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

括弧を使用しない場合、ステートメントは左から右に評価されます。

You can also use parentheses to group clauses, so that you can apply the NOT operator to the group.

キーワード参照

JQL のキーワードは、次のいずれかを行う単語または語句です。

  • 2 つ以上の句を結合して複雑な JQL クエリを形成する
  • 1 つ以上の句のロジックを変更する
  • alters the logic of operators
  • JQL クエリ内に明確な定義がある
  • JQL クエリの結果を変更する特定の関数を実行する

キーワードのリスト:

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.

(warning) EMPTY と NOT EQUALS (!=) は同じではありません。

 

  • 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

Ordering by Components or Versions will list the returned issues first by Project and only then by the field's natural order (see JRA-31113).

^top of keywords | ^^top of topic


演算子参照

An operator in JQL is one or more symbols or words which compares the value of a field on its left with one or more values (or functions) on its right, such that only true results are retrieved by the clause. Some operators may use the NOT keyword.

演算子の一覧:

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

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

  • 要約
  • 説明
  • 環境
  • コメント
  • 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"

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*"
  • 要約に ”issue" および "collector" の単語を含むすべての課題を検索:

    summary ~ "issue collector"
  • 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: !~

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

  • 要約
  • 説明
  • 環境
  • コメント
  • 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"

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.

この演算子では次の述部を使用できます:
  • AFTER "date"
  • BEFORE "date"
  • BY "username"
  • DURING ("date1","date2")
  • ON "date"
この演算子は、フィールドの変更時にシステムで設定された値の名前 (例: "Resolved (解決済み)") を照合します。また、このオプションは値の名前と関連付けられた値 ID も照合します。つまり、"Resolved (解決済み)" と同様に "4" を照合します。

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

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

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

    status WAS "Resolved" BY jsmith BEFORE "2011/02/02"
  • Joe Smith が 2010 年に解決した課題を検索:

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

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

この演算子では次の述部を使用できます:
  • AFTER "date"
  • BEFORE "date"
  • BY "username"
  • DURING ("date1","date2")
  • ON "date"
この演算子は、フィールドの変更時にシステムで設定された値の名前 (例: "Resolved (解決済み)") を照合します。また、このオプションは値の名前と関連付けられた値 ID も照合します。つまり、"Resolved (解決済み)" と同様に "4" を照合します。

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

  • 現在または過去のステータスが "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".

この演算子では次の述部を使用できます:
  • AFTER "date"
  • BEFORE "date"
  • BY "username"
  • DURING ("date1","date2")
  • ON "date"
この演算子は、フィールドの変更時にシステムで設定された値の名前 (例: "Resolved (解決済み)") を照合します。また、このオプションは値の名前と関連付けられた値 ID も照合します。つまり、"Resolved (解決済み)" と同様に "4" を照合します。

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

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

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

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

^top of operators | ^^top of topic

WAS NOT

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

この演算子では次の述部を使用できます:
  • AFTER "date"
  • BEFORE "date"
  • BY "username"
  • DURING ("date1","date2")
  • ON "date"
この演算子は、フィールドの変更時にシステムで設定された値の名前 (例: "Resolved (解決済み)") を照合します。また、このオプションは値の名前と関連付けられた値 ID も照合します。つまり、"Resolved (解決済み)" と同様に "4" を照合します。

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

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

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

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

^top of operators | ^^top of topic

CHANGED

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

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

  • AFTER "日付"
  • BEFORE "日付"
  • BY "ユーザー名"
  • DURING ("日付1","日付2")
  • ON "日付"
  • FROM "古い値"
  • TO "新しい値"
  • 担当者が変更された課題を検索:

    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

フィールド参照

 

最終更新日 2014 年 5 月 4 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.