• Products
  • Documentation
  • Resources

Search for custom fields from plans in JQL

You can use Jira Query Language (JQL) to search for issues with custom issue fields used in your plan. You can search for

  • Parent link

  • Child issues

  • Team field

  • Target start or Target end

To search for child issues of an issue in your plan using the issue's Parent Link:

Syntax

1 "Parent Link"

Alias

1 cf[CustomFieldID]

Field Type

Parent Link relationship

Auto-complete

No

Supported operators

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

Unsupported operators

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

Supported Keywords

1 EMPTY

Examples

  • Get the list of child issues from parent issues: 

    1 "Parent Link" = EX-001
  • Get the child issues from multiple Parent Links: 

    1 "Parent Link" IN (EX-000, EX-001, EX-002, EX-003)
  • Find all issues with no Parent Link:

    1 "Parent Link" IS EMPTY
  • Find all issues that have either EX-001 set as a parent or don't have a parent.

    1 "Parent Link" IN (EX-001, EMPTY)
  • Get the child issues from multiple Parent Links:

    1 "Parent Link" IN (EX-000, EX-001, EX-002, EX-003)

Child issues

To search for child issues of an issue:

Syntax

1 portfolioChildIssuesOf("issue key")

Field Type

JQL function returning issue keys

Auto-complete

No

Supported operators

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

Unsupported operators

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

Supported Keywords

1 EMPTY

Examples

  • To get all child issues below INIT-00 and not just the child issues at the epic hierarchy level:

    1 issuekey in portfolioChildIssuesOf("INIT-001")
  • if you want to return just the story-level issues: 

    1 issuekey in portfolioChildIssuesOf("INIT-001") AND issueType = Story
  • If needed, you can skip returning issues of the hierarchy levels you don't need:

    1 issuekey in portfolioChildIssuesOf("INIT-001") AND issueType != Epic.

Team field

To search for issues, including subtasks, using the Team custom field:

Syntax

1 "Team"

Aliases

1 2 "Team[Team]" cf[CustomFieldID]

Field type

Team Field

Auto-complete

Yes

Note: Selecting the shared team name from the auto-suggested list of team names will replace the actual name of the team in the query with its numerical ID. For example:

1 "Team" = MyTeam → "Team" = 3

Supported operators

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

Unsupported operators

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

Supported Keywords

1 EMPTY

Examples

  • Get the list of issues assigned to a team:

    1 "Team" = "shared team name"
    • Get the list of issues assigned to any set of teams type: 

      1 "Team" IN ("Shared team 1", "Shared team 2", "Shared team 3")
    • Find all issues in the "iOS app development" project that don't have a team assigned:

      1 project = iOS app development and "Team" IS EMPTY
    • Find all stories in the "IOS-76" epic that don't have a team assigned: 

      1 issueKey = IOS-76 and "Team" IS EMPTY
    • Find all issues with no team assigned:

      1 "Team" IS EMPTY

Target start or Target end

To search for issues based on their target start or end date:

Syntax

1 "Target start" /or/ "Target end"

Alias

1 cf[CustomFieldID]

Field type

Target Date Field

Auto-complete

Yes

Note: The auto-suggested list contains JQL functions that returns date-time values where the function name matches the user supplied text. For example:

1 "Target start" = end → endOfDay(), endOfMonth(), endOfWeek(), endOfYear()

Supported operators

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

Unsupported operators

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

Supported Keywords

1 EMPTY

Examples

  • Find all issues with target start after 2 Jan 2020:

1 "Target start" >= "2020-01-02"
  • Find all issues with target start before current timestamp:

1 "Target start" < now()
  • Find all issues with target end earlier than 5 days ago:

1 "Target end" <= -5d
  • Find all issues without a target end date:

1 "Target end" is not EMPTY

Additional Help