-
Bug
-
Resolution: Fixed
-
High
-
4.5.12, 4.13.4
-
1
-
Severity 3 - Minor
-
1
-
Issue Summary
The Security Level field starts being visible / editable in 4.13 when configuring request types for a portal although I was unable to find a specific mention of this feature. However, request types configured with security levels prior to 4.13 are not updated in the database accordingly and thus behave differently even after upgrading
Steps to Reproduce
- Install Service Desk 4.5
- Make Security Level field required
- Add Security Level field to a request type in a service desk
- Note that you cannot make Security Level visible
- Upgrade to Service Desk 4.13
- Add Security Level field to a new request type in a new service desk
- Here you can make Security Level visible
- Go back and observe the 4.5 service desk in unchanged
Expected Results
Service desk projects / request types configured before 4.13 can show the Security Level field accordingly
Actual Results
The underlying database entries are not updated during the upgrade
The below was observed after setting up Service Desk 4.5, upgrading to 4.13, and configuring 2 portals with a few different request types. The unsupported field_type values are from 4.5 and the select field_type values are from 4.13:
select * from "AO_54307E_VIEWPORTFIELD" where "LABEL" = 'Security Level'; DESCRIPTION | DISPLAYED | FIELD_ID | FIELD_ORDER | FIELD_TYPE | FORM_ID | ID | LABEL | REQUIRED -------------+-----------+----------+-------------+-------------+---------+-----+----------------+---------- | f | security | 0 | unsupported | 17 | 68 | Security Level | t | f | security | 0 | unsupported | 1 | 69 | Security Level | t | f | security | 0 | unsupported | 2 | 70 | Security Level | t | f | security | 0 | unsupported | 3 | 71 | Security Level | t | f | security | 0 | unsupported | 4 | 72 | Security Level | t | f | security | 0 | unsupported | 5 | 73 | Security Level | t | f | security | 0 | unsupported | 6 | 74 | Security Level | t | f | security | 0 | unsupported | 7 | 75 | Security Level | t | f | security | 0 | unsupported | 8 | 76 | Security Level | t | f | security | 0 | unsupported | 9 | 77 | Security Level | t | f | security | 0 | unsupported | 10 | 78 | Security Level | t | f | security | 0 | unsupported | 11 | 79 | Security Level | t | f | security | 0 | unsupported | 12 | 80 | Security Level | t | f | security | 0 | unsupported | 13 | 81 | Security Level | t | f | security | 0 | unsupported | 14 | 82 | Security Level | t | f | security | 0 | unsupported | 15 | 83 | Security Level | t | f | security | 0 | unsupported | 16 | 84 | Security Level | t | t | security | 4 | select | 18 | 108 | Security Level | t | t | security | 3 | select | 19 | 109 | Security Level | t | t | security | 3 | select | 20 | 110 | Security Level | t | t | security | 3 | select | 21 | 111 | Security Level | t | t | security | 3 | select | 22 | 112 | Security Level | t | t | security | 3 | select | 23 | 113 | Security Level | t | t | security | 3 | select | 24 | 114 | Security Level | t
Workaround
The following SQL will upgrade the Security Level field on request type configurations:
update "AO_54307E_VIEWPORTFIELD" set "FIELD_TYPE" = 'select' where "LABEL" = 'Security Level' and "FIELD_TYPE" = 'unsupported';
- is caused by
-
JSDSERVER-5113 Make issue security field settable by customer
- Closed
- is related to
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-