-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Low
-
Component/s: Request Type Configuration
-
None
-
1
-
Severity 3 - Minor
Problem
Upon setting up a Required Cascading List custom field and set this field as hidden in the customer request portal. When the parent value configured in the cascading list do not have any child associated and the default value of the field set at the parent level then the request wouldn't be able to be submitted successfully through the portal.
Environment
JSM Cloud
Steps to Reproduce
1. Set up a Cascading List custom field
2. Configure the Parent field and do not configure any values for the Child of the parent
3. In the Jira Service Management project, configure the request type to hide the Cascading List custom field.
4. Configure the default value to be at the parent level and leave the child as NONE
5. Submit the request through the customer portal
Expected Results
Successfully submit the request. As the current behaviour is if there is already a Child value set under the Parent and we set default value of the Child as NONE then it will work.
Actual Results
Unable to submit the request.
Workaround
You need to configure a child value under the parent. After that, if you only configure the default value for the JSM request type at the parent level and leave the child level with NONE it will work.
Notes
Unable to Submit Request Through Portal when there is a hidden cascading list with only parent value set.
- is duplicated by
-
ARMOR-2860 Loading...