-
Bug
-
Resolution: Cannot Reproduce
-
Low
-
None
-
3.12.2, 4.5.1
-
1
-
Severity 2 - Major
-
Issue Summary
Changing the Security Scheme can block request types if the Security field is included as hidden
Steps to Reproduce
- Use one issue security scheme in several projects, including one Service Desk one.
- In the Security scheme set a default Security level.
- Have a request type configured for Email usage.
- For the request type that is used for email add the Security level field as a hidden field (it will be necessary to add it to the screens of that issue type first).
- Create a new Security scheme.
- Change the security scheme of the Service Desk project to the new one, you will be asked to map all the issues already created to the new security levels.
- Send an email to the Service Desk with a user that has the permissions required to create issues).
Expected Results
The email is processed and the issue is visible in queues, and accessible by its reporter and Service Desk agents.
Actual Results
Issues created by email still use the id of the level from the former scheme, and no one can access the issue:
Workaround
- Remove the hidden field from the request type, and add it again, setting the security level for the hidden field value.
- is superseded by
-
JSDSERVER-16169 Migrating issue security schemes corrupts new customer requests if the Issue Security field is preset in JSM Data Center
-
- Closed
-
- mentioned in
-
Page Loading...