Details
-
Bug
-
Resolution: Obsolete
-
Low
-
2
-
Severity 3 - Minor
-
Description
NOTE: This bug report is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding bug report.
We have a project where we enforce privacy via Security Levels.
Repro Settings:
- security level required in Field Config
- security level scheme has a default security level set
- security level is not changeable by the end-user
As an admin, if I now go to configure a Service Desk portal, it will show me an error: "Oops something is broken" and claim that my forms are disabled until I set a value.
This is not true, the forms are still enabled, even if I do not set a value for security level in Service Desk Portal forms.
Expected Result: I think security level is a special field that needs more testing. It probably shouldn't show that error since the forms still display to end-users, nor force users to pre-set a value since it defaults to one anyway.
Workaround
One of the following:
- Disable issue level security for the service desk project
- Change the field configuration to make the issue security an optional field
Attachments
Issue Links
- is related to
-
JSDSERVER-367 Security Level field produces inconsistent errors in Service Desk portal config
- Gathering Impact