Adding a participant to an issue without Request type generates SD notification

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

1. Create an Issue in a service Desk project, from within Jira (not Customer Portal), and do not set any Request Type.
2. 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-4378 JSD not setting requestURL on email notification when request type is empty and the View request link not working: