Can I remove specific notifications from a memeber of customer org. in a project?

[Vera Valshonok]

Hi, community!

Please help me find answer to two of these questions:

1. Is it possible for the project customer organization members not to receive all the notifications when a new ticket is created by any of the Organization members. Can I regulate notifications they get or don't get?

2. Can I create a separate group for users (also including agents) only for one specific issue type in the project that has more than one issue type. I want members of this group to have access only to this issue type.

[Igor Medeiros - Modus Create]

Hi @Vera Valshonok

Adding to what Tobi sent, the disable-and-automate route works but gets noisy as you scale it across organizations or request types. Each rule has to know which users to skip, and there is no shared place to manage exclusions.

If this gets painful across many projects, our app Notification Assistant for Jira lets you replace native customer notifications with custom ones that filter recipients by JQL or user-picker fields, so you can exclude specific org members per request type from one place.

Feel free to reach out if you'd like to see how the recipient rules work.

[Tomislav Tobijas]

Hi @Vera Valshonok ,

Here are answers from my side:

1. Currently, out of the box, you cannot configure system notifications so that they will only be sent to specific members of an organization. There's a related feature request for it: JSDCLOUD-4543: Ability to Disable Notification Within Organisation 
   What you could try is to disable customer notification and build automation rule that would send notifications only to specific users.
2. Can you maybe clarify the use case here? Like, does this group of users contain portal users and agents combined? I believe both cases can be covered if you use separate group (see provided links below)
   I'm asking as there are two types of restrictions when it comes to JSM:
   
   1. Restrictions by request type - where you can restrict who can raise certain request types (which are mapped to work item types).
   2. Restrictions for viewing/editing by work type - we're here talking about work item security schemes.

Hope this helps.

Cheers,
Tobi