-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
3
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Problem Definition
When creating a customer via REST API it's not possible to send notification email to this customer saying that an account has being created for him/her.
Suggested Solution
Add a "notification" parameter on the call, so that users can choose whether to notify the customer or not.
Documentation:
https://docs.atlassian.com/jira-servicedesk/REST/4.17.1/#servicedeskapi/customer
Workaround
None.
- relates to
-
JSDCLOUD-4425 Allow customer notification when created via REST API
- Closed
[JSDSERVER-4425] Allow customer notification when created via REST API
Description |
Original:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-4425]. {panel} h3. Problem Definition When creating a customer via REST API it's not possible to send notification email to this customer saying that an account has being created for him/her. h3. Suggested Solution Add a "notification" parameter on the call, so that users can choose whether to notify the customer or not. h3. Documentation: https://docs.atlassian.com/jira-servicedesk/REST/cloud/#servicedeskapi/customer-createCustomer h3. Workaround None. |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-4425]. {panel} h3. Problem Definition When creating a customer via REST API it's not possible to send notification email to this customer saying that an account has being created for him/her. h3. Suggested Solution Add a "notification" parameter on the call, so that users can choose whether to notify the customer or not. h3. Documentation: https://docs.atlassian.com/jira-servicedesk/REST/4.17.1/#servicedeskapi/customer h3. Workaround None. |
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 [ 3012982 ] | New: JAC Suggestion Workflow 3 [ 3647694 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2665669 ] | New: JAC Suggestion Workflow [ 3012982 ] |
Support reference count | Original: 2 | New: 3 |
Comment | [ A comment with security level 'atlassian-staff' was removed. ] |
Support reference count | New: 2 |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2324703 ] | New: Confluence Workflow - Public Facing v4 [ 2665669 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
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