-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
10.3.3, 10.5.0
-
1
-
Severity 3 - Minor
-
1
-
Issue Summary
Issue cannot be created if the request type contains an hidden Assets custom field having a default value denied in the Filter Issue Scope
Steps to Reproduce
- Create one Assets custom field A with global context.
- Edit the Filter Issue Scope to exclude one object (Ex. Name != 1).
- Add the field to the screen of a JSM project.
- Add the field to a Request type in the JSM project, hide the field and observe that it is possible to filter and select the object excluded in the Filter Issue Scope. This is due to JSDSERVER-15713.
- Assign the excluded object to the hidden field.
- Try to raise an issue in the customer portal.
- When clicking on create the error This form contains a hidden field that does not have a valid default value configured is thrown out:
- In the console while inspecting the error we can see that the affected hidden Assets custom field give an error as the excluded object cannot be found:
"errors": [ { "errorMessage": "This form contains a hidden field that does not have a valid default value configured" }, { "errorMessage": "Could not find Assets object/s (TEST-1)", "field": "customfield_10123" } ], "reasonKey": "validation.error", "reasonCode": "400" }
Expected Results
The issue should be created or the Assets custom field should not allow at all to select the excluded value as hidden value.
Actual Results
The issue is not created with the error displayed above.
Workaround
Either remove the Filter Issue Scope from the custom field configuration or select a different value (not the excluded one) as hidden default value for the field.
Versions Tested
| Testing Requirements | Version | Affected Version | |
|---|---|---|---|
| Customers Reported Version | 10.3.3 - Yes | ||
| Most Recent Bug-Fix Release | 10.5.0 - Yes | ||
| Most Recent LTS |
|
||
| Previous Supported LTS | 5.12.x - No |
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|