-
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
-
-
- Closed
-
-
JSDSERVER-1337 Notify Customer When Ticket Raised "On Behalf Of"
- Closed
-
- Gathering Interest
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[JSDSERVER-1250] Issue raised in behalf of SD Customers doesn't trigger Issue Create notification
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304433 ] | New: JAC Bug Workflow v3 [ 3125391 ] |
| Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 2058494 ] | New: JSD Bug Workflow v5 - TEMP [ 2304433 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2055780 ] | New: JSD Bug Workflow v5 [ 2058494 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 1956360 ] | New: JSD Bug Workflow v5 - TEMP [ 2055780 ] |
| Workflow | Original: JSD Bug Workflow v4 [ 1616075 ] | New: JSD Bug Workflow v5 [ 1956360 ] |
| Description |
Original:
h3.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). h3.Expected Results: The user should receive a notification. h3.Actual Results: The user doesn't receive the email notification on the created issue. h3.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. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1250]. {panel} h3.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). h3.Expected Results: The user should receive a notification. h3.Actual Results: The user doesn't receive the email notification on the created issue. h3.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. |
| Link |
New:
This issue relates to |
| Workflow | Original: JSD Bug Workflow v2 [ 1603277 ] | New: JSD Bug Workflow v4 [ 1616075 ] |
| Workflow | Original: JSD Bug Workflow [ 1399181 ] | New: JSD Bug Workflow v2 [ 1603277 ] |
| Workflow | Original: TTT: Simple Issue Tracking Workflow [ 784415 ] | New: JSD Bug Workflow [ 1399181 ] |