-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
2
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Summary:
The current notification that a customer get when its request is raised by an agent will be like below. It would be great if there is more information about the request as the Customer did not know what is the Request Details looks like. They would need to access the request directly to check for the details
Hi admin, We have received your request and will get back to you soon. – Basic Service Desk
Steps to Reproduce:
- Login as an Agent of a Service Desk project.
- Go to the Customer Portal of the project.
- Raise a request on behalf of a customer.
Current Result:
- The Customer will get a notification that the request is created.
Desired Result:
- The Customer will get a notification that the request is created with the additional details of the request.
- incorporates
-
JSDSERVER-1700 When Raise Request on behalf of customer from JIRA and change request type a notification should be sent
- Gathering Interest
- is duplicated by
-
JSDSERVER-3374 Raising Request on behalf of existing customer should show that its being raised that way
- Closed
- is related to
-
JSDSERVER-3188 Issue Summary missing from the Subject Email Notification
-
- Closed
-
-
JSDSERVER-2263 Provide Summary and Description Information in Service Desk Confirmation Emails Sent to Customers
- Closed
- relates to
-
JSDCLOUD-3221 Improve Notification for Raising Request on behalf of Customer
- Closed
-
JSDSERVER-3931 Allow customers to raise requests on behalf of their colleagues.
- Closed
-
JSDSERVER-4102 As a Service Desk Customer, I'd like the ability to "raise this request on behalf of" other customers
- Gathering Interest
[JSDSERVER-3221] Improve Notification for Raising Request on behalf of Customer
Link | New: This issue relates to JSDSERVER-4102 [ JSDSERVER-4102 ] |
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 ] |
Workflow | Original: JAC Suggestion Workflow [ 3010884 ] | New: JAC Suggestion Workflow 3 [ 3648272 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2664619 ] | New: JAC Suggestion Workflow [ 3010884 ] |
Support reference count | New: 2 |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2325426 ] | New: Confluence Workflow - Public Facing v4 [ 2664619 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JSD Suggestion Workflow [ 2053348 ] | New: JSD Suggestion Workflow - TEMP [ 2325426 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2048425 ] | New: JSD Suggestion Workflow [ 2053348 ] |
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