-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
4.10.0, 4.11.1, 5.12.8
-
6
-
Severity 3 - Minor
-
1
-
Issue Summary
When an issue type is changed on a ticket, it will break the request type mapping and the request type field will be displayed as No match. However, if the ticket is viewed in the issue navigator list view, the request type field shows the previous request type value so searching for request type null/empty would not return a value.
Steps to Reproduce
- Create a service desk ticket via Jira UI not selecting a Customer Request Type.
- Set a Customer Request Type
- Change the issue type of the ticket.
Expected Results
The request type shows no match and the field is empty in the issue navigator list view.
Actual Results
The request type shows no match and the field shows the previous value in the issue navigator list view.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
JSDSERVER-6395 Customer Request Type retaining Old Value in Issue Navigator
-
- Closed
-
-
JSDSERVER-6506 Invalid request type behavior when moving a Service Desk request to a new project
-
- Closed
-
- links to