-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
3.10.0, 3.12.0
-
7
-
Severity 3 - Minor
-
0
-
Issue Summary
- A participant added to an issue without Request type generates SD notification. Normally, when the request type is missing from an issue in a Service Deks project, no Customer (SD) notifications are sent but, for some reason, adding a participant to the issue will trigger a Customer notification.
Steps to Reproduce
- Create an Issue in a service Desk project, from within Jira (not Customer Portal), and do not set any Request Type.
- Add a participant to the issue created.
Expected Behavior
- If there is no request type set in the issue, no Customer Notifications are triggered.
Actual Behavior
- If there is no request type set in the issue, adding a user to the Participants field will trigger customer notifications for this event.
Cause
- Unknown.
Workaround
- Do not create issues using the Create button. You can also remove the Service Desk agents from the Create issues permission in the Permission scheme of the project, to force them to create issues from the Customer Portal.
- Follow the KB Automatically set Customer Request Type When Issue is Created via JIRA to configure Jira to automatically set the request type when missed.
Notes:
- This behavior can only be provoked from within Jira by Agents as Customers do not see the requests from the customer portal when the issue does not have a request type and once the request type has been set, it cannot be removed.
- This notification leads to other issues, like the one registered in the bug ticket
JSDSERVER-4378JSD not setting requestURL on email notification when request type is empty and the View request link not working:
- causes
-
-
- Closed
-
- is blocked by
-
JSMDC-3541 You do not have permission to view this issue
- links to
- mentioned in
-
Page Failed to load
[JSDSERVER-5673] Adding a participant to an issue without Request type generates SD notification
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | Original: Notifications cqt ril | New: Notifications cleanup-seos-fy25 cqt ril |
| Labels | Original: Notifications cqt | New: Notifications cqt ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 955057 ] |
| Remote Link | Original: This issue links to "JSDS-3541 (Bulldog)" [ 461779 ] | New: This issue links to "JSMDC-3541 (JIRA Server (Bulldog))" [ 461779 ] |
| UIS | Original: 2 | New: 0 |
| UIS | Original: 1 | New: 2 |
| UIS | Original: 2 | New: 1 |
| UIS | Original: 0 | New: 2 |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Service Management Data Center