Cascading Issue Picker

Field configuration

Before starting the field configuration, please follow the instructions for creating custom fields: Create a Custom Field

Step 1: Set a name and description

Provide a good name for the new custom field. Make it descriptive, concise, and easy to understand for others who will use it. Avoid using ambiguous or overly technical terms.

Step 2: Default configuration

The Cascading Issue Picker can be utilized without additional configuration. For advanced configuration options, refer to the following sections.

Step 3 (optional): Skip permission check

Using this option allows you to bypass Jira permissions in service requests and make all selected issues visible (read-only) to anyone with access to the current service request in your Jira.

You can differ between then Request View and the autocomplete in the Request Form.

Please be careful when using this option and make sure you are aware of the impact.

Needed to be compatible with Jira Service Management

Enabling the “Skip permission check“ options bypass standard Jira permission checks for service requests, making the selected issues read-only and visible to anyone with access to the current request. Use with caution: Ensure you understand the implications of exposing issue data to a broader audience.

Step 4: Display options and required selection

Use Display Options to choose whether the full cascade path (e.g., Epic > Story > Sub-Task) or only the final selection is shown in the issue sidebar. Enable Required Selection to ensure users complete all available levels before the field can be saved.

Step 5: Settings per Level

Each of the up to three levels can be configured individually.

You can assign a custom name, apply specific JQL filters, or limit the number of displayed issues.

A level will only display issues that are children of the selected issue in the level above and that also match the defined JQL.

Step 5.1 (optional): add custom JQL including placeholders

To refine the selection of issues available for linking in the issue picker, you have the option to supply custom JQL (Jira Query Language). Additionally, you can employ placeholders that are dynamically replaced with the current issue context.

Placeholders

Consider using the issue picker in a project like 'ACF'; your JQL might appear as follows before and after replacement:

project = {{project.key}} → project = ACF

You may use the following placeholders:

{{issue.key}}, {{issue.type}}, {{project.key}}, {{project.type}}

Placeholder usage is limited to the issue view and may not be applicable in the issue create form and JSM request form. Using placeholders will generate an invalid JQL query in the search. For testing purposes, replace them with specific issue information.

Field view and edit

Field edit

The "Select Issue" autocomplete initially offers a selection of recently accessed issues. You can search for issues based on either the summary or the issue key. It will on show children of the upper level.

Field view

Linked issues are displayed with their key, summary, and status. Clicking a key opens the corresponding issue in a new tab.

Levels are visually separated using the configured level names, providing clear structure and context.

Related Use Cases

More use cases are coming soon. In the meantime, check out our other use cases.

Jira Service Management (JSM)

Request form

As Jira user

As a Jira user (internal customer), you have the ability to utilize the issue picker within the request form, just as you would in a standard issue form.

As customer

As an (external) customer, you can view both your own requests and those created by your organization, just as they appear in the portal view under "Requests".

Portal view

The Cascading Issue Picker links are visible to both internal and external customers.

JQL expression

The Issue Picker field can be accessed like this.

${fieldName}.Issues1: string[]
${fieldName}.Issues2: string[]
${fieldName}.Issues3: string[]

Find further information here Find specific work items | Jira Cloud | Atlassian Support

Example: perform a search for all issues that are linked with issue CMSP-19

"Issue Picker.Issues1" = CMSP-36

Data Structure (Automation)

Use custom fields with automation

{
  "keys1": string[],
  "keys2": string[],
  "keys3": string[]
}

Example: The current issue links with an Epic CMSP-36, Stories CMSP-38, CMSP-37 and Sub-Tasks CMSP-41, CMSP-39, CMSP-40.

{
  "keys1": [
    "CMSP-36"
  ],
  "keys2": [
    "CMSP-38",
    "CMSP-37"
  ],
  "keys3": [
    "CMSP-41",
    "CMSP-39",
    "CMSP-40"
  ]
}