-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
4
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? 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
-
JSDSERVER-4373 Incorrect Notification Helper for Issue Moved
-
- Closed
-
-
JSDSERVER-4489 Redirect a Moved Request to its JIRA URL if Portal URL is Not Available and Anonymous View is Enabled
- Closed
- is incorporated by
-
JSDSERVER-4506 Customer Notifications for Issue Updated Event
- Gathering Interest
- relates to
-
JSDCLOUD-3417 Issue Moved notification
- Closed
[JSDSERVER-3417] Issue Moved notification
Resolution | Original: Won't Do [ 10000 ] | New: Low Engagement [ 10300 ] |
Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
UIS | Original: 1 | New: 0 |
UIS | Original: 2 | New: 1 |
Workflow | Original: JAC Suggestion Workflow [ 3012603 ] | New: JAC Suggestion Workflow 3 [ 3651176 ] |
UIS | Original: 3 | New: 2 |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2664653 ] | New: JAC Suggestion Workflow [ 3012603 ] |
UIS | Original: 2 | New: 3 |
UIS | Original: 1 | New: 2 |
Hi,
Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.
To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.
Regards,
Jira Service Management, Server & Data Center