Details
-
Bug
-
Resolution: Fixed
-
High
-
105
-
Severity 3 - Minor
-
10
-
Description
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 ticket via the customer portal. Make sure the request type is valid.
- 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.
Notes
This affect both tickets when changing the issue type directly or moving issues to own/other projects.
Attachments
Issue Links
- is duplicated by
-
JSDCLOUD-9181 Wrong request type in the queue and filter view after changing the issue type
- Long Term Backlog
- relates to
-
JSDCLOUD-1835 Update request type upon issue type change.
- In Progress
- duplicates
-
ECOHELP-8046 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...