-
Bug
-
Resolution: Fixed
-
High
-
5.2.6, 7.2.4, 7.12.2, 8.6.0, 8.13.6
-
5.02
-
23
-
Severity 2 - Major
-
55
-
-
Summary
Required field validation works only on the first Cascading drop-down list
Steps to replicate
- Add a Select list (cascading) field
- In the field configuration, add some options for that field
- Make that field required
- Add it to an issue
- Only select the first field from the drop-down
- Save the form
Expected results
You get an error from Jira because the 2nd drop-down was not filled out, and it's required
Actual results
Form saves without errors
Workaround
Use the Suite Utilities for JIRA plugin and the "Field Required" workflow validator
- You would add this to the Create Transition and also make the field required
- You need to make the field required so that it will show the red asterisk indicating that it is required
- duplicates
-
JRASERVER-10302 Ability to make both fields required in Cascading Select CF
- Closed
- is duplicated by
-
JRASERVER-31422 Cascading Select should be consistent related the Required option
- Closed
- is related to
-
JRASERVER-76711 Allow child options in cascading drop-downs to be optional
- Gathering Interest
- relates to
-
JSDSERVER-14225 Getting the error "The following hidden fields on the request type do not have the required preset values:" when a cascading field is set to "Required"
- Closed
-
FLASH-3605 Loading...
-
FLASH-3789 Loading...
- Mentioned in
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...