-
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
| Assignee | New: Rachel Crossman [ rcrossman@atlassian.com ] |
| Link |
New:
This issue relates to |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| Status | Original: Long Term Backlog [ 12073 ] | New: In Progress [ 3 ] |
| Support reference count | Original: 1 | New: 2 |
| Description |
Original:
*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 !sample_1.PNG|thumbnail! # In the new issue view, Move to another issue type with a different request type value !sample_2.PNG|thumbnail! *Expected Results* The request type value is empty. !sample_3.PNG|thumbnail! *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. |
New:
*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 !sample_1.PNG|thumbnail! # In the new issue view, Move to another issue type with a different request type value *Expected Results* The request type value is empty. !sample_2.PNG|thumbnail! *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. !sample_3.PNG|thumbnail! *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. |
| Status | Original: Needs Triage [ 10030 ] | New: Long Term Backlog [ 12073 ] |
| Component/s | New: Issue View [ 46701 ] | |
| Component/s | Original: Request Type Configuration [ 46711 ] |
| Support reference count | New: 1 |