-
Bug
-
Resolution: Fixed
-
Low
-
None
-
2
-
Minor
-
Summary
When performing the "Move" action from one issue type to another, the "Request Type" value stays the same, in reality when such a change is done, it should show "None".
Steps to Reproduce
- Create a Service Desk ticket with a request type value
- In the new issue view, Move to another issue type with a different request type value
Expected Results
The request type value is empty.
Actual Results
The request type value has the same value as the previous issue type which is incorrect. If you change to "Old Issue View", it will show "No Match" for the request type, which is the expected outcome.
Effect
From the customer point of view, it is still visible and accessible despite having the wrong request type value. So the customer communication is still valid.
Workaround:
Switch to old issue view to key in the value in the "Request Type" field.
- relates to
-
JSDCLOUD-1835 Update request type upon issue type change.
- Closed
[JSDCLOUD-8640] Request Type shows incorrect value in New Issue View after performing Move action
We have identified that our customer is affected because when the request type is not filled he cannot see the ticket description on the customer portal.
Hi all,
I'm Michael, a developer on Jira Service Desk.
A fix for this bug has been released.
Issues that have an "invalid" request type (which is what happens when an issue is moved to a new issue type) will now show the request type as empty. An agent may then select a valid request type.
This should now have the same behaviour as in the old issue view.
If you are still having issues with the behaviour of request types in the new issue view please raise a new support ticket (and mention this ticket if you think the problem may be related).
Thanks