-
Bug
-
Resolution: Fixed
-
Low
-
None
-
33
-
Severity 2 - Major
-
7
-
Summary
Wrong request type in the queue and filter view after changing the issue type in one project or moving between projects
Steps to Reproduce
- Move a service desk issue across projects - or - simply change the issue type on one issue on one project
- While moving the issue, change the issue type - or - change the issue type on one issue for one project
- After moving the issue, the request type field will be empty in the issue view:
- But in the queue view/filter view, the request type will be mapped with a value from the source project
Expected Results
The Request type value should be empty as well in the queue/filter view
Actual Results
The request type has a value from the source project
Workaround
No workaround
- duplicates
-
JSDCLOUD-5901 Request type field shows previous request type value in issue navigator list view
- Closed
- relates to
-
JSDCLOUD-5807 Inconsistent database value for Request Type prevents "moving" issues to a different type and "editing"
- Closed
-
JSDCLOUD-1835 Update request type upon issue type change.
- Closed
(2 mentioned in)