-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
5.13.0, 5.15.0, 5.15.3, 10.3.0, 10.2.2, 10.3.6
-
1
-
Severity 3 - Minor
-
Issue Summary
After upgrading JSM from 5.12 to 10.3, customer users are unable to open new request from portal. The error message indicates that "This form contains a hidden field that does not have a valid default value configured".
Steps to Reproduce
- Create a Assets Custom field.
- Within the request types, Hide this custom field with preset values.
- Proceed to create a new request from the customer portal using any customer user, and the request creation fails with an error.
Expected Results
The expected behaviour is that, despite the presence of a hidden field with a preset value, the request creation process should function without any errors.
Actual Results
Request creation fails in portal with error
Workaround
Enable access for customers
- Open your object schema in Assets.
- At the top-right, select Object schema > Configure.
- Switch to the Roles tab.
- In the Jira Service Management information box at the bottom, select Enable.
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Hi everyone,
This is Sam Xu from the JSM DC team. Thank you for bringing this issue to our attention.
The permission validation for hidden fields is working as designed within JSM Data Center's security model. Hidden fields are subject to the same permission checks as visible fields to maintain data integrity and security consistency. This behaviour wasn't observed in version 5.12 because the Assets Custom Field lacked proper backend validation implementation at that time.
To set the right expectations, we are closing this bug as ‘Won’t Fix' as we do not have any plans to change the behaviour of this feature. If this behaviour has a significant impact on your work, please share examples with us to help us understand your use cases when using this feature.
Thank you again for providing valuable feedback to our team! I will be marking it closed for now.
Sam Xu