-
Suggestion
-
Resolution: Duplicate
-
0
-
5
-
NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.
Problem Definition
Currently, after moving an Issue from SD.A to SD.B, there will be no notification email on this. Hence, replying to the Issue creation notification email will not update the Issue. This is due to the request type is being mapped on the Issue when the Issue is being moved.
Suggested Solution
At the Issue Moved wizard, on "Update Fields", prompt the user to map the Request Type.
Workaround
For now, manually set the Request Type and add a comment so that the customer will receive a notification email on the Issue Moved.
- incorporates
-
JSDCLOUD-4373 Incorrect Notification Helper for Issue Moved
- Closed
-
JSDCLOUD-4489 Redirect a Moved Request to its JIRA URL if Portal URL is Not Available and Anonymous View is Enabled
- Closed
- is duplicated by
-
JSDCLOUD-3613 Allow For Selecting Customer Request Types When Moving Issues Between SD Projects
- Closed
- is incorporated by
-
JSDCLOUD-4506 Customer Notifications for Issue Updated Event
- Gathering Interest
- is related to
-
JSDSERVER-3417 Issue Moved notification
- Closed
- relates to
-
JSDCLOUD-3613 Allow For Selecting Customer Request Types When Moving Issues Between SD Projects
- Closed
- mentioned in
-
Page Loading...