Require child option on cascading select field in Jira Cloud

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

Platform Notice: Cloud Only - This article only applies to Atlassian products on the Cloud platform.

Currently, a required cascading select field doesn't require a value in the child or sub-option list. After selecting a Parent value, the Child value can still be set as None.

Please refer to the following feature request ticket: JRACLOUD-32463 - Required "Select List (cascading)" custom field allows user to set child value to None if the field has a default value

Solution

Workaround: Use Automation and smart values to validate child select list value

As a workaround in the meantime, we can use Automation and Smart values to validate that the child value on the Cascading field is not empty.

If it is empty, the automation can:

  • Transition the ticket back to an Open or In progress status (to prevent issue closure with invalid field data)

  • Add a comment mentioning the initiator (the user who performed the action) to request they fix the field

  • Send an email notification to the initiator to request they fix the field

To create the automation rule:

  1. Open the project, and select Project settings > Automation

  2. Select Create rule

  3. Select your desired trigger > Next

  4. Select IF: Add a condition > {{smart value}} condition

  5. In the First value, enter the following:

    • {{issue.customfield_•••.child.value}}

    • Replace ••• with the field ID

    • Find the custom field's ID using this document

  6. In Condition, select equals

  7. In Second value, leave it empty

  8. Select Next

From here, choose your desired Action for the automation rule

If you want to transition the ticket to an Open or In progress status

  1. Select THEN: Add an Action > Transition issue

    1. Note: to transition a ticket between statuses using automation, the transition between those statuses has to exist in the workflow

If you want to add an internal comment mentioning the user who transitioned the ticket

  1. Select THEN: Add an Action > Comment on issue

  2. In Comment visibility, make sure it is set as Internal only

  3. In Comment, you can mention them using the following:

    • [~accountId:{{initiator.accountId}}]

If you want to send an email to the user who transitioned the ticket

  1. Select THEN: Add an Action > Send email

  2. In To, select Initiator

    1. You can use the {{issue.url}} smart value under the content to provide them with the URL of the issue

Finally, give your rule a name and click on Turn it on

An example automation rule appears in the screenshot below:

automation rule example. the rule has been configured as described in the article, using the send email action, and transitions the issue to a waiting for customer status.
Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.