Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Customer Notifications are not being sent


When configuring your Customer Notifications and a Customer is also added as a Watcher on a Jira Issue as well, no Notification is sent out to that Customer Why is that?

Root cause

You don't have Jira Notifications enabled for Customers under Settings > Products > Jira Service Management - Configuration

Screenshot 2023-05-30 at 10.17.45 AM.pngAs a Watcher triggers a Jira Notification and a Customer is also a part of a Jira Issue this will trigger sending out a Notification for both Notification Types. Also, if Jira Notifications are enabled for Customers they will receive both Customer and Jira Notifications, however, it will essentially create duplicate event Notifications, one email for internal Users and one email for external Customers. If you want to keep this setting as recommended (turned off), there is an alternative solution available:

Solution: Automation Rule to Notify Customer is also a Watcher

Here we are creating an Automation Rule on the Issue Created Trigger, with a re-fetch Issue Data Action (to ensure the Customer Field Values are populated when the Rule executes):

Screenshot 2023-05-30 at 11.02.21 AM.png

Then we create a Branch Rule Component with a Smart Value of: {{participant}} for the Request Participant field. This then has an advanced compare condition of if: {{issue.Watchers}} contains {{participants.accountId}} to see if the account Id is listed as both a Watcher and Customer on the ticket:Screenshot 2023-05-30 at 11.02.28 AM.png

After that, we are creating a Send Web Request Action to get the List of Users account Id

Screenshot 2023-05-30 at 11.08.47 AM.png

Send an email to the email addresses who were listed as Request Participants and also a Watcher on the Jira Issue. The Web Request URL would be similar to the following as a GET request:

* Web Request URL -{{participant.accountId.urlEncode}}

Screenshot 2023-05-30 at 11.08.58 AM.png

Related articles

* Get User Web Request -

* How to troubleshoot customer notifications in Jira Service Management Cloud -


I hope this helps!

Christian B.


1 comment

Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 30, 2023

Why would you make a customer a Watcher on an issue? 🤔

Watchers are for internal users/agents, Request Participants are for (portal-only) Customers.

Quite a complex "workaround" if you ask me.

Like Dominik Březina likes this


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events