How to Fix Customer Notification Issues in Jira Service Management Cloud

Is this a valid Jira Service Management request?

Check that the ticket is in a Service Management space. Make sure the "Request Type" field is populated.

Can the customer see the ticket under "My Requests" in the customer portal?

Check if the customer is the reporter, request participant, or member of an organization the ticket is being shared with. Organization members only receive the first notification of the ticket being shared with that organization, and they must access the ticket from the portal to opt in for the following notifications of that ticket. More details can be found in Everything we should know about customer organizations in Jira Service Management projects.

If an issue is moved from one space to another, we will need to add the users or reporter from the old space to the new space as well. We can either add the user from: Service Space > Customers page - Add a customer to a service space as a portal-only customer or Service Space > Space Settings > People page - Add users to your space as users with any available roles in the space.

Are customer notifications enabled in Jira Service Management?

Enable them in the space settings: Go to the Space settings page > Notifications > Customer notifications.

Is the user the reporter, request participant, or member of an organization the ticket is shared with?

Add the customer as a participant to the ticket or to the organization that the ticket is shared with.

Is the user subscribed to receive customer notifications?

Ask them to open the request on the customer portal, and click on Notifications Off under the request's status to turn it On.

Were all translations reviewed in the Language support settings?

Go to Space settings > Language support and check if there are yellow marks next to a language added to your space:

In this case, you can either remove the unwanted languages or confirm each pending review by clicking on each language, selecting each component with the yellow mark, and clicking on Confirm translation.

Does the ticket have an issue security set?

(For Company-managed space only)

Open the request and check if it has an issue security level. In this case, ensure the customer role is added under security levels in the issue security scheme associated with your space (Space settings > Access > Issue security). Add "Service Desk Customer - Portal Access" role to the security level.

The security level lock icon will only appear if there's a security scheme set for the space, and if the Security level field is added to the View/Edit screen. Only users with permission can set the issue security level.

Does the customer have a valid email address?

Invite the correct email address under the Customers page and replace the customer account in the ticket:

Open the service space, then click Customers in the sidebar.

Does the customer have duplicate accounts using the same email address?

Please see how to check if they have duplicate accounts and the solution in the following document: Permission and access issues due to duplicate accounts.

Have you tested the email address?

Try sending an email outside of Jira, using a separate email account, to check if the emails are routing.

Are you having issues sending out notifications only for the Resolved and Reopened actions?

Please see Service Management Notifications not sent on Resolved or Reopened Requests.

Are you having issues sending out only customer satisfaction surveys?

Please check the following document to find the most common reasons for this behavior: How to troubleshoot when a customer satisfaction survey is not being sent in the Jira Service Management Cloud.

Is the notification to customers going as plain text?

You can manage the Email format to change the format by going to: As a Jira administrator, click on the Cog icon in the right corner > System > Default user preferences. Choose HTML or plain text for customer notifications.

Does the customer not have an issue as a watcher at the point the notification should have been triggered?

Remove the customer from the watcher list. To prevent future issues, you can create an automation rule to automatically remove the customer from the watcher list, especially for reporters.