詳細検索 - フィールド リファレンス

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

ここでは高度な検索に使用するフィールドに関する情報について説明します。

A field in JQL is a word that represents Jira's default field or a custom field that has already been defined in your Jira applications.

In a clause, the field is followed by an operator. The operator is followed by one or more values or functions. The operator compares the value of the left side with one or more values or functions on the right side. So, only valid results are retrieved by the clause. But you can't compare two fields in JQL.

If your fields have localized names, you still should use the original Jira syntax of these fields. Advanced search doesn't identify localizations. 

対象バージョン

Search for issues that are assigned to a particular affected versions. You can search by version name or version ID (the unique number that Jira automatically allocates to a version).

It's better to search by version ID than by version name because:

  • Different projects may have versions with the same name.
  • Your Jira admin might change the name of a version. Such change might break saved filters that rely on that name.

Version IDs are unique and can't be changed.

構文
affectedVersion
フィールド タイプVERSION
オートコンプリートはい
サポートされる演算子

= , != , > , >= , < , <= , ~ , !~
IS, IS NOT, IN, NOT IN

  • The comparison operators use the versions' order that has been set up by your project admin, not a numeric or alphabetical order.
  • The contain operators find exact matches and can be used to search through versions with a wildcard.
サポートされない演算子
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
サポートされる関数When used with the IN and NOT IN operators, this field supports:
  • releasedVersions()
  • latestReleasedVersion()
  • unreleasedVersions()
  • earliestUnreleasedVersion()
  • Find issues with an AffectedVersion of 3.14:
    affectedVersion = "3.14"
    • Full stops are reserved characters that should be put in quotation marks.
  • AffectedVersion が "Big Ted" である課題を検索:
    affectedVersion = "Big Ted"
  • AffectedVersion ID が 10350 である課題を検索:
    affectedVersion = 10350

^ ページのトップへ

On this page:

承認

Search for issues that have been approved or require approval. The search can be further refined by user.

The field is only applicable if Jira Service Desk (Jira Service Management) is installed and licensed and if you're using the Approvals functionality.

構文
承認
フィールド タイプUSER
オートコンプリート

いいえ

サポートされる演算子

=

サポートされない演算子~ , != , !~ , > , >= , < , <=
IS , IS NOT , IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数
  • approved()
  • approver()
  • myApproval()
  • myPending()
  • pending()
  • pendingBy()
  • John Smith による承認が必要または必要だった課題を検索:
    approval = approver(jsmith)

  • John Smith による承認が必要な課題を検索:
    approval = pendingBy(jsmith)

  • 現在のユーザーによる承認が必要な課題を検索:
    approval = myPending()

  • 承認が必要なすべての課題を検索:
    approval = pending()

^ ページのトップへ

担当者

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

構文
担当者
エイリアス
cf[CustomFieldID]
フィールド タイプUSER
オートコンプリート

はい

サポートされる演算子

= , !=

  • The comparison operators use the versions' order that has been set up by your project admin, not a numeric or alphabetical order.

IS, IS NOT, IN, NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED

サポートされない演算子 ~ , !~ , > , >= , < , <=
サポートされる関数
  • When used with the IN and NOT IN operators, this field supports membersOf().
  • When used with the = and != operators, this field supports currentUser().
  • John Smith に割り当てられた課題を検索:
    assignee = "John Smith"
    または
    assignee = jsmith

  • Find issues that are currently assigned or were previously assigned to John Smith:
    assignee WAS "John Smith" 
    or
    assignee WAS jsmith

  • Find issues that are assigned by the user with the email address "bob@mycompany.com":
    assignee = "bob@mycompany.com"

Full stops and at signs (@) are reserved characters that should be put in quotation marks.

^ ページのトップへ

添付ファイル

Search for issues that have or don't have attachments. 

構文
attachments
フィールド タイプATTACHMENT
オートコンプリートはい
サポートされる演算子IS, IS NOT
サポートされない演算子=, != , ~ , !~ , > , >= , < , <= IN, NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
サポートされる関数なし
  • 添付ファイルを持つ課題を検索:
    attachments IS NOT EMPTY  

  • Search for issues that don't have attachments:
    attachments IS EMPTY 

^ ページのトップへ

カテゴリ

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

構文
category
フィールド タイプCATEGORY
オートコンプリートはい
サポートされる演算子=, !=
IS, IS NOT, IN, NOT IN
サポートされない演算子~ , !~ , > , >= , < , <= WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
サポートされる関数なし

Find issues that belong to projects in the "Alphabet Projects" category:
category = "Alphabet Projects"

^ ページのトップへ

コメント

Search for issues with a comment that contains particular text. Jira text-search syntax can be used.

構文
comment
フィールド タイプTEXT
オートコンプリート

いいえ

サポートされる演算子

~ , !~

サポートされない演算子 = , != , > , >= , < , <=
IS, IS NOT, IN, NOT IN,
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
サポートされる関数なし

Find issues where a comment contains the fuzzy or exact phrase "My PC is quite old":
comment ~ "My PC is quite old"

^ ページのトップへ

コンポーネント

Search for issues that belong to a particular components of a project. You can search by component name or component ID (the unique number that Jira automatically allocates to a component).

It's better to search by component ID than by component name because:

  • Different projects may have components with the same name.
  • Your Jira admin might change the name of a component. Such change might break saved filters that rely on that name.

Component IDs are unique and can't be changed.

構文
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, this field supports componentsLeadByUser().

  • "Comp1" または "Comp2" コンポーネントを持つ課題を検索:
    component in (Comp1, Comp2)
  • Find issues in the "Comp1" and "Comp2" components:
    component in (Comp1) and component in (Comp2)
    or
    component = Comp1 and component = Comp2 
  • Find issues in the component with the ID 20500:
    component =  20500 

^ ページのトップへ

作成日

Search for issues that were created on, before, or after a particular date or date range. If the time component isn't specified, midnight will be assumed. Search results will be relative to your 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).

Also, use quotation marks. If you omit quotation marks, the number in a search query will be interpreted as milliseconds after epoch (1970-1-1).

構文
created
エイリアス
createdDate
フィールド タイプDATE
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT , IN , NOT IN

サポートされない演算子 ~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
サポートされる関数

When used with the comparison operators, this field supports:

  • currentLogin()
  • lastLogin()
  • now()
  • startOfDay()
  • startOfWeek()
  • startOfMonth()
  • startOfYear()
  • endOfDay()
  • endOfWeek()
  • endOfMonth()
  • endOfYear()
  • Find all issues created before December 12, 2010:
    created < "2010/12/12"
  • Find all issues created on or before December 12, 2010:
    created <= "2010/12/13"
  • Find all issues created on December 12, 2010, before 2:00 pm:
    created > "2010/12/12" and created <  "2010/12/12 14:00" 
  • 1 日以内に作成された課題を検索:
    created > "-1d"
  • Find issues created in January 2011:
    created > "2011/01/01" and created <  "2011/02/01"
  • Find issues created on January 15, 2011, or any other particular date, including your today's date:
    created > "2011/01/15" and created <  "2011/01/16"

^ ページのトップへ

作成者

特定のユーザーが作成した課題を検索します。検索条件にはユーザーのフルネーム、ID またはメール アドレスを使用できます。

構文
creator
フィールド タイプUSER
オートコンプリート

はい

サポートされる演算子

= , !=
IS , IS NOT , IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN

サポートされない演算子 ~ , !~ , > , >= , < , <=
CHANGED
サポートされる関数
  • When used with the IN and NOT IN operators, this field supports membersOf().
  • When used with the = and != operators, this field supports currentUser().
  • Search for issues that were created by Jill Jones:
    creator = "Jill Jones"
    or
    creator = "jjones"
  • "bob@mycompany.com" のメール アドレスを持つユーザーが作成した課題を検索:
    creator = "bob@mycompany.com"

Full stops and at signs (@) are reserved characters that should be put in quotation marks.

^ ページのトップへ

カスタム フィールド

Custom fields are applicable only if your Jira admin has created them.

Search for issues where a particular custom field has a particular value. You can search by custom field name or custom field ID (the unique number that Jira automatically allocates to a custom field).

It's better to search by custom field ID than by custom field name because:

  • A custom field may have the same name as Jira's default field. In this case, Jira will search for the default field and not for the custom one.
  • Your Jira admin might change the name of a custom field. Such change might break saved filters that rely on that name.

Custom field IDs are unique and can't be changed.

構文
CustomFieldName
エイリアス
cf[CustomFieldID]
フィールド タイプDepends on the custom field's configuration. Jira text-search syntax can be used with custom fields of the type Text.
オートコンプリート

Yes for custom fields of the following types: picker, group picker, select, checkbox, and radio button.

サポートされる演算子

カスタム フィールドの種類に応じて、サポートされる演算子も異なります。

サポートされる演算子:
数値と日付フィールドの場合 

= , != , > , >= , < . <=
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
サポートされない演算子 ~ , !~ , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
サポートされる関数

Different types of custom fields support different functions.

サポートされる関数:
日付/時間フィールドの場合 

When used with the comparison operators, this field supports:

  • currentLogin()
  • lastLogin()
  • now()
  • startOfDay()
  • startOfWeek()
  • startOfMonth()
  • startOfYear()
  • endOfDay()
  • endOfWeek()
  • endOfMonth()
  • endOfYear()
サポートされる関数:
バージョン ピッカー フィールドの場合 
When used with the IN and NOT IN operators, this field supports:
  • releasedVersions()
  • latestReleasedVersion()
  • unreleasedVersions()
  • earliestUnreleasedVersion()
  • Find issues where the value of the Location custom field is "New York":
    location = "New York"
  • Find issues where the value of the custom field with the ID 10003 is "New York":
    cf[ 10003 ] = "New York"
  • Find issues where the value of the Location custom field is "London" or "Milan" or "Paris":
    cf[ 10003 ] in ( "London"  "Milan"  "Paris" )
  • Find issues where the Location custom field has no value:
    location != empty

^ ページのトップへ

顧客リクエスト タイプ

The field is only applicable if Jira Service Desk (Jira Service Management) is installed and licensed.

Search for issues that match a specific customer request type in a Service Desk project. You can search for a customer request type either by name or description configured in the Request Type configuration screen.

Note that the Lucene value for the customer request type is  portal-key/request-type-key .

While the portal key can't be changed after a Service Desk portal is created, the project key can be changed. The request type key can't be changed once the request type is created.

構文
"Customer Request Type"
フィールド タイプカスタム フィールド
オートコンプリート

はい

サポートされる演算子
= , !=  

IN , NOT IN

サポートされない演算子

~ , !~ , > , >= , < , <=
IS , IS NOT, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

Note that the Lucene value for Customer Request Type is  portal-key/request-type-key .

While the portal key can't be changed after a service desk portal is created, the project key can be changed. The Request Type key can't be changed once the Request Type is created.

サポートされる関数

なし

  • Find issues where the customer request type is Request a new account in projects the user has access to:
    "Customer Request Type" = "Request a new account"
  • Find issues where the customer request type is Request a new account in a SimpleDesk project where the value after an operator is a Lucene value selected from the autocomplete suggestion list:
    "Customer Request Type" =  "sd/system-access"
  • Find issues where the customer request type is either Request a new account or Get IT Help:
    "Customer Request Type" IN ( "Request a new account", "Get IT Help")

^ ページのトップへ

説明

Search for issues where the description contains particular text. Jira text-search syntax can be used.

構文
description
フィールド タイプTEXT
オートコンプリート

いいえ

サポートされる演算子

~ , !~
IS , IS NOT

サポートされない演算子 = , != , > , >= , < , <=
IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

なし

Find issues where the description contains the fuzzy or exact phrase "Please see screenshot":
description ~  "Please see screenshot"

^ ページのトップへ

期限

Search for issues that were due on, before, or after a particular date or date range. Note that the due date relates to the date only and not to the time.

以下の形式のいずれかを使用:

  • "yyyy/MM/dd"
  • "yyyy-MM-dd"

Or use "w" (weeks) or "d" (days) to specify a date relative to the current date. Use quotation marks.

構文
due
エイリアス
dueDate
フィールド タイプDATE
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT , IN , NOT IN

サポートされない演算子 ~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

When used with the comparison operators, this field supports:

  • currentLogin()
  • lastLogin()
  • now()
  • startOfDay()
  • startOfWeek()
  • startOfMonth()
  • startOfYear()
  • endOfDay()
  • endOfWeek()
  • endOfMonth()
  • endOfYear()
  • Find all issues due before December 31, 2010:
    due <  "2010/12/31"
  • Find all issues due on or before December 31, 2010:
    due <=  "2011/01/01"
  • Find all issues due tomorrow:
    due =  "1d"
  • Find all issues due in January 2011:
    due >=  "2011/01/01" and due <=  "2011/01/31"
  • Find all issues due on January 15, 2011, or any other particular date, including your today's date:
    due =  "2011/01/15"

^ ページのトップへ

環境

Search for issues where the environment contains particular text. Jira text-search syntax can be used.

構文
environment
フィールド タイプTEXT
オートコンプリート

いいえ

サポートされる演算子

~ , !~
IS , IS NOT

サポートされない演算子 = , != , > , >= , < , <=
IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

なし

Find issues where the environment contains the fuzzy or exact phrase "Third floor":
environment ~  "Third floor"

^ ページのトップへ

Search for issues that belong to a particular epic. The search is based on either the epic's name, issue key, or issue ID (the unique number that Jira automatically allocates to an issue).

構文
"epic link"
フィールド タイプEpic Link Relationship
オートコンプリート

はい

サポートされる演算子

= , !=
IS , IS NOT, IN , NOT IN

サポートされない演算子 ~ , !~ , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

When used with the IN or NOT IN operators, this field supports:

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

Find issues that belong to the epic "Jupiter", where "Jupiter" has the issue key ANERDS-31:
"epic link" = ANERDS-31
or
"epic link" = Jupiter

^ ページのトップへ

フィルター

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

  • It's better to search by filter ID than by filter name. The filter name might be changed, so another saved filter that uses this filter name might be broken. But filter IDs are unique and cannot be changed.
  • An unnamed link statement in your query will override an ORDER BY statement in the saved filter.
  • You can't run or save a filter that may cause an infinite loop. This means you can't reference a saved filter if it references your current filter.
構文
filter
エイリアス
request、savedFilter、searchRequest 
フィールド タイプフィルター
オートコンプリート

はい

サポートされる演算子

= , !=
IN , NOT IN

サポートされない演算子 ~ , !~ , > , >= , < , <=
IS , IS NOT, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

なし

Search the results of the filter "My Saved Filter" with the ID 12000 for issues assigned to the user jsmith:
filter = "My Saved Filter" and assignee = jsmith
or
filter = 12000 and assignee = jsmith

^ ページのトップへ

修正バージョン

Search for issues that are assigned to a particular fix version. You can search by version name or version ID (the unique number that Jira automatically allocates to a version).

It's better to search by version ID than by version name because:

  • Different projects may have versions with the same name.
  • Your Jira admin might change the name of a version. Such change might break saved filters that rely on that name.

Version IDs are unique and can't be changed.

構文
fixVersion
フィールド タイプVERSION
オートコンプリート

はい

サポートされる演算子

= , != , > , >= , < , <= , ~ , !~
IS , IS NOT, IN , NOT IN, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED 

  • The comparison operators use the versions' order that has been set up by your project admin, not a numeric or alphabetical order.
  • The contain operators find exact matches and can be used to search through versions with a wildcard.
サポートされる関数

When used with the IN and NOT IN operators, this field supports:

  • releasedVersions()
  • latestReleasedVersion()
  • unreleasedVersions()
  • earliestUnreleasedVersion()
  • Find issues with the affected version 3.14 or 4.2:
    fixVersion in ("3.14","4.2")
    • Full stops are reserved characters that should be put in quotation marks.
  • Find issues with the fix version "Little Ted":
    fixVersion = "Little Ted"
  • Find issues with the fix version with the ID 10001:
    fixVersion = 10001

^ ページのトップへ

課題キー

Search for issues with a particular issue key or issue ID (the unique number that Jira automatically allocates to an issue).

構文
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, this field supports:

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

Find the issue with the key "ABC-123":
issueKey = ABC- 123

^ ページのトップへ

課題リンク タイプ

Issue linking allows you to create associations between issues on either the same or different Jira servers. For example, an issue may duplicate another issue or depend on the resolution of another issue. You can find detailed information about issue links in Configuring issue linking.

When searching for issues with a particular link type, you can only find linked issues that are on the same Jira instance where you're searching. Links to issues on a remote Jira instance or to Confluence pages won't be included.

tip/resting Created with Sketch.

Use the following JQL query to add colors to your issue cards. For example, add a red stripe to issues that have blockers and keep all other issues green.

This will help you provide the right information to your team at a glance. For more details, see Customizing cards.

構文
issueLinkType
オートコンプリート

はい

サポートされる演算子

= , !=
IN , NOT IN

サポートされない演算子 ~ , !~  , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED , IS , IS NOT
サポートされる関数

なし

  • Find issues with the link type "blocks":
    issueLinkType = blocks
  • Find issues with the issue type "duplicates" or "is duplicated by":
    issueLinkType in (duplicates,"is duplicated by")
  • Find issues with link types other than “clones”:
    issueLinkType != clones
    (info) This query will also return issues with no links at all.
  • Find issues that are blocked by other issues or that don't have any blockers:
    issueLinkType = "is blocked by"
    issueLinkType != "is blocked by"

^ ページのトップへ

ラベル

Search for issues tagged with a label or list of labels. You can also search for issues without any labels to identify what issues should be tagged so that they show up in relevant sprints, queues, or reports. 

構文
labels
フィールド タイプLABEL
オートコンプリート

はい

サポートされる演算子

= , !=, IS, IS NOT, IN, NOT IN

We recommend using IS or IS NOT to search for a single label and IN or NOT IN to search for a list of labels.

サポートされない演算子~ , !~ , , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
サポートされる関数なし
  • 既存のラベルを持つ課題を検索:
    labels = "x"
  • 特定のラベルを持たない課題と、ラベルを持たない課題を検索:
    labels not in ("x") or labels is EMPTY

最終閲覧日

Search for issues that were last viewed on, before, or after a particular date or date range. If the time component isn't specified, midnight will be assumed. Search results will be relative to your 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).

Also, use quotation marks. If you omit quotation marks, the number in a search query will be interpreted as milliseconds after epoch (1970-1-1).

構文
lastViewed
フィールド タイプDATE
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT, IN , NOT IN

サポートされない演算子 ~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED 
サポートされる関数

When used with the comparison operators, this field supports:

  • currentLogin()
  • lastLogin()
  • now()
  • startOfDay()
  • startOfWeek()
  • startOfMonth()
  • startOfYear()
  • endOfDay()
  • endOfWeek()
  • endOfMonth()
  • endOfYear()
  • Find all issues last viewed before December 12, 2010:
    lastViewed < "2010/12/12"
  • Find all issues last viewed on or before December 12, 2010:
    lastViewed <= "2010/12/13"
  • Find all issues last viewed on December 12, 2010, before 2:00 pm:
    lastViewed > "2010/12/12" and created <  "2010/12/12 14:00"
  • 最終閲覧日から 1 日以内の課題を検索:
    lastViewed > "-1d"
  • Find issues last viewed in January 2011:
    lastViewed > "2011/01/01" and created <  "2011/02/01"
  • Find issues last viewed on January 15, 2011, or any other particular date, including your today's date:
    lastViewed > "2011/01/15" and created <  "2011/01/16"

^ ページのトップへ

レベル

The field is available only if your Jira admin has enabled issue level security.

Search for issues with a particular security level. You can search by issue level security name or issue level security ID (the unique number that Jira automatically allocates to an issue level security).

It's better to search by security level ID than by security level name because your Jira admin might change the name of a security level. Such change might break saved filters that rely on that name. Security level IDs are unique and can't be changed.

構文
レベル
フィールド タイプSECURITY LEVEL
オートコンプリート

はい

サポートされる演算子

= , !=
IS , IS NOT, IN , NOT IN

サポートされない演算子 > , >= , < , <= , ~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED 
サポートされる関数

なし

  • Search for issues with the security level "Really High" or "level1":
    level in ( "Really High" , level1)
  • Search for issues with the security level with the ID 123:
    level =  123

^ ページのトップへ

初期見積

The field is available only if your Jira admin has enabled time tracking.

Search for issues where the original estimate is set to a particular value. The value is a number, not a date or date range.

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

構文
originalEstimate
エイリアス
timeOriginalEstimate
フィールド タイプDURATION
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT, IN , NOT IN

サポートされない演算子 ~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED 
サポートされる関数

なし

  • Find issues with the original estimate of one hour:
    originalEstimate = 1h
  • Find issues with the original estimate of more than two days:
    originalEstimate > 2d

^ ページのトップへ

The field is available only if your Jira admin has enabled sub-tasks.

Search for all sub-tasks of a particular issue. You can search by issue key or by issue ID (the unique number that Jira automatically allocates to an issue).

構文
parent
フィールド タイプISSUE
オートコンプリート

いいえ

サポートされる演算子

= , !=
IN , NOT IN

サポートされない演算子 > , >= , < , <= , ~ , !~
IS , IS NOT, WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED 
サポートされる関数

なし

Find issues that are sub-tasks of the issue TEST-1234:
parent = TEST- 1234

^ ページのトップへ

Priority

Search for issues with a particular priority. You can search by priority name or priority ID (the unique number that Jira automatically allocates to a priority).

It's better to search by priority ID than by priority name because your Jira admin might change the name of a priority. Such change might break saved filters that rely on that name. Priority IDs are unique and can't be changed.

構文
優先度
フィールド タイプPRIORITY
オートコンプリート

はい

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT, IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED 

サポートされない演算子 ~ , !~
サポートされる関数

なし

  • Find issues with the priority "High":
    priority = High
  • Find issues with the priority with the ID 10000:
    priority =  10000

^ ページのトップへ

プロジェクト

Search for issues that belong to a particular project. You can search by project name, by project key, or by project ID (the unique number that Jira automatically allocates to a project).

In the rare case, a project key of one project may be the same as the name of another project. In the search, the project key of the first project will be preferred to the name of the second. So, the search results won't contain anything from the second 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, this field supports:

  • projectsLeadByUser()
  • projectsWhereUserHasPermission()
  • projectsWhereUserHasRole()
  • Find issues that belong to a project with the name "ABC Project":
    project =  "ABC Project"
  • Find issues that belong to the project with the key "ABC":
    project =  "ABC"
  • Find issues that belong to the project with the ID "1234":
    project =  1234

^ ページのトップへ

残余見積

The field is available only if your Jira admin has enabled time tracking.

Search for issues where the original estimate is set to a particular value. The value is a number, not a date or date range.

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

構文
remainingEstimate
エイリアス
timeEstimate
フィールド タイプDURATION
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT, IN , NOT IN

サポートされない演算子 ~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED 
サポートされる関数

なし

Find issues with the remaining estimate of more than four hours:
remainingEstimate > 4h

^ ページのトップへ

報告者

Search for issues that were reported by a particular user. The user may be the same as the creator. You can search by the user's full name, ID, or email address.

構文
reporter
フィールド タイプUSER
オートコンプリート

はい

サポートされる演算子

= , !=
IS , IS NOT, IN , NOT IN ,
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

サポートされない演算子~ , !~ , > , >= , < , <=
サポートされる関数
  • When used with the IN and NOT IN operators, this field supports membersOf().
  • When used with the comparison operators, this field supports currentUser().
  • Search for issues that were reported by Jill Jones:
    reporter =  "Jill Jones"
    or
    reporter =  jjones
  • Search for issues that were reported by the user with email address bob@mycompany.com:
    reporter =  "bob@mycompany.com"

Full stops and at signs (@) are reserved characters that should be put in quotation marks.

^ ページのトップへ

リクエストのチャンネル タイプ

The field is only applicable if Jira Service Desk (Jira Service Management) is installed and licensed.

Search for issues that were requested through a specific channel. For example, issues submitted via email or through a Service Desk portal.

構文
request-channel-type
フィールド タイプTEXT
オートコンプリート

はい

サポートされる演算子

= , !=

IS, IS NOT, IN, NOT IN

サポートされない演算子  ~ , !~ ,  > , >= , < , <= 
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
サポートされる関数

When used with the IN and NOT IN operators, this field supports:

  • email: メールで作成されたリクエスト
  • Jira: requests created by using Jira
  • portal: requests created by using a Service Desk portal
  • api: requests created by using a REST API

  • リクエスト チャンネルがメールである課題を検索:
    request-channel-type = email

  • Find issues where the request channel was something other than a Service Desk portal:
    request-channel-type != portal

^ ページのトップへ

リクエストの最終アクティビティ時刻

The field is only applicable if Jira Service Desk is installed and licensed.

Search for issues that were last created or active on, before, or after a particular date or date range. If the time component isn't specified, midnight will be assumed. Search results will be relative to your 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).

Also, use quotation marks. If you omit quotation marks, the number in a search query will be interpreted as milliseconds after epoch (1970-1-1).

構文
request-last-activity-time
フィールド タイプDATE
オートコンプリート

はい

サポートされる演算子

= , != , > , >= , < , <=

IS, IS NOT, IN, NOT IN

サポートされない演算子  ~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
サポートされる関数

When used with the comparison operators, this field supports:

  • currentLogin()
  • lastLogin()
  • now()
  • startOfDay()
  • startOfWeek()
  • startOfMonth()
  • startOfYear()
  • endOfDay()
  • endOfWeek()
  • endOfMonth()
  • endOfYear()

  • Find all issues last active before May 23, 2016:
    request-last-activity-time <  "2016/05/23"
  • Find all issues last active on before May 23, 2016:
    request-last-activity-time <=  "2016/05/23"
  • Find all issues created on May 23, 2016, and last active before 2:00 pm that day:
    created >  "2016/05/23" AND request-last-activity-time <  "2016/05/23 14:00" 
  • Find issues last active less than one day ago:
    request-last-activity-time >  "-1d"
  • Find issues last active in January 2016:
    request-last-activity-time >  "2016/01/01" and request-last-activity-time <  "2016/02/01"

^ ページのトップへ

ソリューション

Search for issues that have a particular resolution. You can search by resolution name or resolution ID (the unique number that Jira automatically allocates to a resolution).

It's better to search by resolution ID than by resolution name because your Jira admin might change the name of a resolution. Such change might break saved filters that rely on that name. Resolution IDs are unique and can't be changed.

構文
resolution
フィールド タイプRESOLUTION
オートコンプリート

はい

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT, IN , NOT IN ,
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

サポートされない演算子~ , !~
サポートされる関数

なし

  • Find issues with the resolution "Cannot Reproduce" or "Won't Fix":
    resolution in ("Cannot Reproduce", "Won't Fix")
  • Find issues with the resolution with the ID 5:
    resolution = 5
  • Find issues that don't have a resolution:
    resolution = unresolved

^ ページのトップへ

解決済み

Search for issues that were resolved on, before, or after a particular date or date range. If the time component isn't specified, midnight will be assumed. Search results will be relative to your 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).

Also, use quotation marks. If you omit quotation marks, the number in a search query will be interpreted as milliseconds after epoch (1970-1-1).

構文
resolved
エイリアス
resolutionDate
フィールド タイプDATE
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT, IN , NOT IN

サポートされない演算子~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

When used with the comparison operators, this field supports:

  • currentLogin()
  • lastLogin()
  • now()
  • startOfDay()
  • startOfWeek()
  • startOfMonth()
  • startOfYear()
  • endOfDay()
  • endOfWeek()
  • endOfMonth()
  • endOfYear()
  • Find all issues that were resolved before December 31, 2010:
    resolved <=  "2010/12/31"
  • Find all issues that were resolved on December 31, 2010, before 2:00 pm:
    resolved <  "2010/12/31 14:00"
  • Find all issues that were resolved on or before December 31, 2010:
    resolved <=  "2011/01/01"
  • Find issues that were resolved in January 2011:
    resolved >  "2011/01/01"   and resolved <  "2011/02/01"
  • Find issues that were resolved on January 15, 2011, or any other particular date, including your today's date:
    resolved >  "2011/01/15"   and resolved <  "2011/01/16"
  • Find issues that were resolved in the last hour:
    resolved > -1h

^ ページのトップへ

SLA

The field is used in Jira Service Desk (Jira Service Management) only.

Search for requests whose SLAs are in a certain status or condition.

構文
Time to resolution

Time to first response

<your custom SLA name>
フィールド タイプSLA
オートコンプリート

いいえ

サポートされる演算子

= , !=, > , >= , < , <=

サポートされない演算子~ , !~
IS , IS NOT , IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数
  • breached()
  • completed()
  • elapsed()
  • everBreached()
  • paused()
  • remaining()
  • running()
  • withinCalendarHours()
  • Find issues where Time to First Response was breached:
    "Time to First Response" = everBreached()

  • Find issues where an SLA for Time to Resolution is paused due to a condition:
    "Time to Resolution" = paused()

  • Find issues where an SLA for Time to Resolution is paused due to the SLA calendar:
    "Time to Resolution" = withinCalendarHours()

  • Find issues that have been waiting for a response for more than one hour:
    "Time to First Response" > elapsed("1h")

  • Find issues that that will breach Time to First Response in the next two hours:
    "Time to First Response" < remaining("2h")

^ ページのトップへ

Sprint

Search for issues that are assigned to a particular sprint. This works for active sprints and future sprints. The search is based on either the sprint name or the sprint ID (the unique number that Jira automatically allocates to a sprint).

If you have multiple sprints with similar or identical names, you can search by using the sprint name or even a part of it. The possible matches will be shown in the autocomplete dropdown along with the sprint dates to help you distinguish between them. The sprint ID will also be shown in parentheses.

構文
sprint
フィールド タイプNUMBER
オートコンプリート

はい

サポートされる演算子

= , !=
IS , IS NOT, IN , NOT IN

サポートされない演算子 ~ , !~ , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数
  • openSprints()
  • closedSprints()
  • Find issues that belong to the sprint 999:
    sprint =  999
  • Find issues that belong to the sprint "February 1":
    sprint =  "February 1"
  • Find issues that belong to either "February 1", "February 2", or "February 3":
    sprint in ( "February 1" , "February 2" , "February 3" )
  • Find issues that are assigned to any sprint:
    sprint is not empty

^ ページのトップへ

ステータス

Search for issues that have a particular status. You can search by status name or status ID (the unique number that Jira automatically allocates to a status).

It's better to search by status ID than by status name because your Jira admin might change the name of a status. Such change might break saved filters that rely on that name. Status IDs are unique and can't be changed.

構文
ステータス
フィールド タイプSTATUS
オートコンプリート

はい

サポートされる演算子

= , !=
IS , IS NOT, IN , NOT IN ,
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED

The WAS, WAS NOT, WAS IN, and WAS NOT IN operators can only be used with the status name, not with the ID.

サポートされない演算子 ~ , !~ , > , >= , < , <=
サポートされる関数

なし

  • Find issues with the status "Open":
    status = Open
  • Find issues with the status ID 1:
    status =  1
  • Find issues that currently have or previously had the status "Open":
    status WAS Open

^ ページのトップへ

要約

Search for issues where the summary contains particular text. Jira text-search syntax can be used.

構文
要約
フィールド タイプTEXT
オートコンプリート

いいえ

サポートされる演算子

~ , !~
IS , IS NOT

サポートされない演算子 = , != , > , >= , < , <=
IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

なし

Find issues where the summary contains the fuzzy or exact phrase "Error saving file":
summary ~  "Error saving file"

^ ページのトップへ

Text

This is a master field that allows you to search all text fields:

  • 要約
  • 説明
  • 環境
  • コメント
  • Custom fields that use the free text searcher, including custom fields of the following built-in custom field types:
    • フリー テキスト フィールド (無制限のテキスト)
    • テキスト フィールド (255 文字未満)
    • 読み取り専用テキスト フィールド
構文
text
フィールド タイプTEXT
オートコンプリート

いいえ

サポートされる演算子

~

サポートされない演算子 = , != , !~ , > , >= , < , <=
IS , IS NOT , IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

なし

  • Find issues where the text field matches the word "Fred":
    text ~ "Fred"
    or
    text ~ Fred
  • Find all issues where the text field contains the fuzzy or exact phrase "full screen":
    text ~  full screen

^ ページのトップへ

消費時間

The field is available only if your Jira admin has enabled time tracking.

Search for issues where the time spent is set to a particular value. The value is a number but not a date or date range.

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

構文
timeSpent
フィールド タイプDURATION
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT , IN , NOT IN

サポートされない演算子 ~ , !~ 
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

なし

Find issues where the time spent is more than five days:
timeSpent > 5d

^ ページのトップへ

タイプ

Search for issues that have a particular issue type. You can search by issue type name or issue type ID (the unique number that Jira automatically allocates to an issue type).

It's better to search by type ID than by type name because your Jira admin might change the name of a type. Such change might break saved filters that rely on that name. Type IDs are unique and can't be changed.

構文
type
エイリアス
issueType
フィールド タイプISSUE_TYPE
オートコンプリート

はい

サポートされる演算子

= , !=
IS , IS NOT , IN , NOT IN

サポートされない演算子 ~ , !~  , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

なし

  • Find issues with the issue type "Bug":
    type = Bug
  • Find issues with the issue type "Bug" or "Improvement":
    issueType in(Bug,Improvement)
  • Find issues with the issue type ID 2:
    issueType = 2

^ ページのトップへ

更新日

Search for issues that were last updated on, before, or after a particular date or date range. If the time component isn't specified, midnight will be assumed. Search results will be relative to your 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).

Also, use quotation marks. If you omit quotation marks, the number in a search query will be interpreted as milliseconds after epoch (1970-1-1).

構文
updated
エイリアス
updatedDate
フィールド タイプDATE
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT , IN , NOT IN

サポートされない演算子 ~ , !~ 
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

When used with the comparison operators, this field supports:

  • currentLogin()
  • lastLogin()
  • now()
  • startOfDay()
  • startOfWeek()
  • startOfMonth()
  • startOfYear()
  • endOfDay()
  • endOfWeek()
  • endOfMonth()
  • endOfYear()
  • Find issues that were last updated before December 12, 2010:
    updated < "2010/12/12"
  • Find issues that were last updated on or before December 12, 2010:
    updated <"2010/12/13"
  • Find all issues that were last updated before 2:00 pm on December 31, 2010:
    updated <"2010/12/31 14:00"
  • Find issues that were last updated more than two weeks ago:
    updated < "-2w"
  • Find issues that were last updated on January 15, 2011, or any other particular date, including your today's date:
    updated > "2011/01/15" and updated < "2011/01/16"
  • 最終更新日が 2011 年 1 月である課題を検索:
    updated > "2011/01/01" and updated < "2011/02/01"
  • 2020 年 1 月 1 日以降に更新されたすべての課題を検索:
    updated >= "2020/01/01"

^ ページのトップへ

投票者

Search for issues for which a particular user has voted. You can search by the user's full name, ID, or email address.

You'll only find issues for which you have the View Voters and Watchers permission, unless you're searching for your own votes. For more details, see votedIssues.

構文
voter
フィールド タイプUSER
オートコンプリート

はい

サポートされる演算子

= , !=
IS , IS NOT , IN , NOT IN

サポートされない演算子 ~ , !~ , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数
  • When used with the IN and NOT IN operators, this field supports membersOf().
  • When used with the comparison operators, this field supports currentUser().
  • 自身が投票した課題を検索:
    voter = currentUser()
  • Find issues that the user jsmith has voted for:
    voter = "jsmith"
  • Find issues for which a member of the Jira-administrators group has voted:
    voter in membersOf("Jira-administrators")

^ ページのトップへ

投票数

Search for issues with a particular number of votes.

構文
votes
フィールド タイプNUMBER
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IN , NOT IN

サポートされない演算子 ~ , !~ 
IS , IS NOT , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

なし

12 票以上の投票数を持つすべての課題を検索:
votes >= 12

^ ページのトップへ

ウォッチャー

Search for issues that a particular user is watching. You can search by the user's full name, ID, or email address.

You'll only find issues for which you have the View Voters and Watchers permission, unless you're searching for issues where you're the watcher. For more details, see watchedIssues.

構文
watcher
フィールド タイプUSER
オートコンプリート

はい

サポートされる演算子

= , !=
IS , IS NOT , IN , NOT IN

サポートされない演算子 ~ , !~ , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数
  • When used with the IN and NOT IN operators, this field supports membersOf().
  • When used with the comparison operators, this field supports: currentUser().
  • 自身がウォッチしている課題を検索:
    watcher = currentUser()
  • Find issues that the user jsmith is watching:
    watcher = "jsmith"
  • Search for issues that are being watched by a member of the Jira-administrators group:
    watcher in membersOf("Jira-administrators")

^ ページのトップへ

ウォッチャー

Search for issues with a particular number of watchers.

構文
watchers
フィールド タイプNUMBER
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IN , NOT IN

サポートされない演算子 ~ , !~ 
IS , IS NOT , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

When used with the IN and NOT IN operators, this field supports membersOf().

When used with the comparison operators, this field supports: currentUser().

Find all issues that are being watched by more than three people:
watchers > 3

^ ページのトップへ

作業ログの作成者

The field is available only if your Jira admin has enabled time tracking.

You'll only find issues for which you have the View Voters and Watchers permission, unless you're searching for issues where you've logged your work.

Search for issues where a particular user has logged their work. You can search by the user's full name, ID, or email address. 

構文
worklogAuthor
フィールド タイプUSER
オートコンプリート

はい

サポートされる演算子

= , !=
IS , IS NOT , IN , NOT IN

サポートされない演算子 ~ , !~ , > , >= , < , <=
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

When used with the IN and NOT IN operators, this field supports membersOf().

When used with the comparison operators, this field supports: currentUser().

  • Find issues where you've logged your work:
    worklogAuthor = currentUser()
  • Find issues where the user jsmith has logged work:
    worklogAuthor = "jsmith"
  • Find issues where a member of the Jira-software-users group has logged work:
    worklogAuthor in membersOf("Jira-software-users")

^ ページのトップへ

作業ログへのコメント

The field is available only if your Jira admin has enabled time tracking.

Search for issues with a comment in a work log entry which contains particular text. Jira text-search syntax can be used.

構文
worklogComment
フィールド タイプTEXT
オートコンプリート

いいえ

サポートされる演算子

~ , !~

サポートされない演算子 = , != , > , >= , < , <=
IS , IS NOT , IN , NOT IN , WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

なし

Find issues with a comment in a work log entry that contains the fuzzy or exact phrase "test sessions":
comment ~  "test sessions"

作業ログの日付

The field is available only if your Jira admin has enabled time tracking.

Search for issues with comments in work log entries that were created on, before, or after a particular date or date range. If the time component isn't specified, midnight will be assumed. Search results will be relative to your 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).

Also, use quotation marks. If you omit quotation marks, the number in a search query will be interpreted as milliseconds after epoch (1970-1-1).

構文
worklogDate
フィールド タイプDATE
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT , IN , NOT IN

サポートされない演算子 ~ , !~
WAS, WAS IN, WAS NOT, WAS NOT IN, CHANGED
サポートされる関数

When used with the comparison operators, this field supports:

  • currentLogin()
  • lastLogin()
  • now()
  • startOfDay()
  • startOfWeek()
  • startOfMonth()
  • startOfYear()
  • endOfDay()
  • endOfWeek()
  • endOfMonth()
  • endOfYear()
  • Find issues that have comments in work log entries created before midnight of December 12, 2010:
    worklogDate < "2010/12/12"
  • Find issues that have comments in work log entries created on or before December 12, 2010, but not on December 13, 2010:
    worklogDate <= "2010/12/13"
  • Find issues that have comments in work log entries created on December 12, 2010, before 2:00 pm:
    worklogDate > "2010/12/12" and worklogDate <  "2010/12/12 14:00" 
  • 作業ログ エントリに 1 日以内に作成されたコメントを持つ課題を検索:
    worklogDate > "-1d"
  • Find issues that have comments in work log entries created in January, 2011:
    worklogDate > "2011/01/01" and worklogDate <  "2011/02/01"
  • Find issues that have comments in work log entries created on January 15, 2011, or any other particular date, including your today's date:
    worklogDate > "2011/01/15" and worklogDate <  "2011/01/16"

^ ページのトップへ

作業率

The field is available only if your Jira admin has enabled time tracking.

Search for issues where the work ratio has a particular value. Work ratio is calculated as follows: 

workRatio = (timeSpent / originalEstimate) x 100

構文
workRatio
フィールド タイプNUMBER
オートコンプリート

いいえ

サポートされる演算子

= , != , > , >= , < , <=
IS , IS NOT , IN , NOT IN

サポートされない演算子 ~ , !~ 
WAS, WAS IN, WAS NOT, WAS NOT IN , CHANGED
サポートされる関数

なし

  • Find issues where more than 75% of the original estimate has been spent:
    workRatio > 75

^ ページのトップへ

最終更新日: 2023 年 2 月 1 日

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

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