nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Prevent notification for organizations but use Request participants

Arnold Leenders

Using the Jira SD you can configure notifications using project settings > customer notifications.

The To is either Reporter and/or Customers Involved.

The Customers involved group includes Organizations and is large and do not require any update mails, only the Request Participants should be on CC. How can I achieve that?

The Organizations allow these users to lookup such a ticket if they want so for that reason we can not reduce that.

thx

Accepted answers

Brant Schroeder

@Arnold Leenders Welcome to the Atlassian community

The delivered customer notifications will not allow you to distinguish between the two. You can use an app like JEMH that allows for more email configuration. If you wanted to you could always set the notification to reporter and then set up an automation to email the request participants.

All comments

Brant Schroeder

@Arnold Leenders Welcome to the Atlassian community

Arnold Leenders

Hi Brant, ended up deleting the std rules and added an automation:

When: Rule is triggered on
Comment is the main action

If: Compare two values
Checks if:
{{comment.internal}} equals false

Initiator is in
Initiator is in
jira-users

Then: Send email
Reporter, Request participants, pending approvers
Issues {{issue.key}} : {{issue.summary}}
was updated

Email:

To*
Reporter
Cc
Request participants
Bcc
Subject*
Issue {{issue.key}} : {{Issue.summary}} was updated
Content*
{{issue.comment.last.author.displayName}} commented:

{{issue.comment.last.body}}
More options
From

Bojana_xnbokn

Hi @Arnold Leenders & @Brant Schroeder

Let me share with you the answer I got from Atlassian and I can confirm it is working as expected. Actually JSM supports what we are trying to achive.

All what you have to do is to either disable "Organization added notification" completely or to set To: Customer Involved instead of Added Organisationfor the "Organization added" notification. Once you do any of the above you will ensure that only reporter and request participants receive any other notifications and not the entire organization even if the organization is set in the issue. So, Organisation-added settings mainly manage the notification that is sent to people in the Organisation.

But please note that this will impact all notifications and when you share a ticket manually with an organisation it won't trigger a notification to all customers from the organisation but to users who are added as request participants and also belong to the same organisation.

One more thing which is worth mentioning is that even if you would use "Organization added notification" and set To: Added Organisation, the organization members would get only one notification where they are informed about the issue and suggested to visit the portal in order to view the request and select Get notifications to follow along, meaning no further notifications will be sent unless they visit the portal and select Get notifications for this issue.

There is no official documentation about this, but as I have heard it is on the way!

Hope this helps!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-desk-cloud

jira-service-management-cloud

jira-service-management