-
Suggestion
-
Resolution: Unresolved
-
391
-
125
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Atlassian update: Dec 2023
Hi all, thank you for your continued interest in this ticket. There's been some discussion on whether this is a feature request or a bug - we've assessed it as a Feature Request:
There are 2 expected behaviours of this field. On the one hand, we have this ticket open to make it so that both parent and child field values are required. Removing the “None” value will not solve the issue as it is a placeholder option and you would still be able to create an issue without a child value assigned. On the other hand, we have customers who expect that field to work as it does today, that the Parent value is required but the child can be filled in later. This behaviour has existed in Jira Cloud since it was made available.
Addressing it as a bug would impact the expected behaviour for a significant number of our customers as it would be a feature change for them. Alternatively, we would have to make cascading field select more configurable to support both behaviours, which would be a feature request. Unfortunately, we are unable to work on this at this point in time due to competing priorities. Sorry that this is not better news, we will update this ticket should it be prioritised in the future.
—
Currently, when making a cascading select list which has a default designated a required field, the none option is still present and an acceptable value.
The behavior for this should mimic the select list where the none option is removed once the cascading select is set to required and has a default set.
This feature request refers to the second value of the Select List (cascading) custom field. It's not possible to leave the first field with a value of "None" but it is possible to do this for the second:
It should not be possible to leave a value of None for the second field.
Workaround
As an alternative, we can use Automation and Smart values to validate that the child value on the Cascading field is not empty and if it is, perform some actions. The steps to create the automation rule are described in the following document:
- is duplicated by
-
JRACLOUD-82897 Allow workflow validator on cascading field value both parent & child
- Closed
- is related to
-
JRACLOUD-10302 Ability to make both fields required in Cascading Select CF
- Closed
-
JRACLOUD-7320 Allow me to change the "None" in custom fields
- Gathering Interest
-
JRASERVER-32463 Remove None option if Cascading select list is required and has a default selected
- Gathering Interest
-
JSDCLOUD-6199 How do I make the second field of a cascading select field mandatory?
- Gathering Interest
- relates to
-
JRACLOUD-7687 Remove 'None' option if select list is required and has a default selected
- Closed
-
JRACLOUD-72704 Allow Select List (cascading) Child - second value to be required
- Closed
-
JRACLOUD-83238 Add support to conditions with fields based on other fields in the issue creation process
- Closed
-
JRACLOUD-42041 Allow removing "none" option for non-required Custom Fields, or allow required by screen
- Gathering Interest
-
JRACLOUD-62567 Conditionally or dynamically mandatory / required custom field based on the value of another field
- Gathering Interest