-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
None
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Steps to Reproduce:
- Add a newly created user (with default application access groups on creation) to the Service Desk Customer role.
- Configure Notification Scheme to make sure that this new user is part of the Issue Create event . Alternatively can also include Reporter to the event.
- Create a new ticket and assign the Reporter role to the user (on creation).
Expected Results:
The user should receive a notification.
Actual Results:
The user doesn't receive the email notification on the created issue.
Workaround:
This seems to only affect Service Desk Customers specifically. If added into another role; the user will be able to receive the notification normally on issue create.
- relates to
-
JSDCLOUD-1250 Issue raised in behalf of SD Customers doesn't trigger Issue Create notification
-
- Closed
-
-
JSDSERVER-1337 Notify Customer When Ticket Raised "On Behalf Of"
- Closed
-
JSDSERVER-1700 When Raise Request on behalf of customer from JIRA and change request type a notification should be sent
- Gathering Interest
- mentioned in
-
Page Failed to load
Form Name |
---|
Version 2.1 of JIRA Service Desk has added the Raise this request on behalf of feature in the customer portal.
WIth this, an agent can enter the customer portal (from the queue page to not hinder productivity) and raise a request on behalf of a customer. From within the portal, the customer will receive the created notification.
Currently the flow is not possible from JIRA. Some additional information is provided at https://confluence.atlassian.com/display/Cloud/Configuring+JIRA+Service+Desk+notifications
JSD-1700 has been raised as a suggestion to do something similar from JIRA context, and any feedback or additional information will be appreciated on that ticket.
Regards
Matt
JIRA Service Desk developer