For us it's very important to get this feature. 

The communication is difficult and requires much more time and effort.

It would be good to have the "notifications" on - by default.

This would be great to have this functionality, even if it is in the initial e-mail when you can click the link to automatically enable notifications

This is a big dealbreaker for us, along with the lack of any intuitive way to send outgoing messages to users without first receiving a support request.

8c40a346214e Correct.

We rarely have changes in users so it's not a problem for us and we don't have to pay for another plugin.

If you have an open ServiceDesk where anyone can join, yes it's a problem then.

7d019277ac00 But then you have to manually edit the automation every time there is a change of members, no?

Here's a cheap workaround: 

Create the following in Project Automation:   

Rule name: Add participants for organization XXX 

• Trigger: Issue created
• If condition: Issue fields condition - Organizations equals "XXX" 
• Action: Edit issue - Request Participants
  • Add the people you want
  • More options: disable the notification

This way, the people you add will always be participants to all issues and will receive all notifications.

Really? And who is going to pay for the recommended app?

We recommend using the In-App Customer Portal Notifications app, which provides more flexible notification management directly within the Customer Portal. This app allows Organization Members to receive real-time notifications for all relevant updates by default, without needing to opt in manually. 

App Links: In-App Customer Portal Notifications for Jira

We are open to feature requests and would be happy to discuss further enhancements to meet your team’s needs.

Please get this resolved. 

It would be great to have organization as variable that you can choose for in email notifications by default. Only way to get round this is by automation which obviously you charge for after hitting a threshold. Atlassian aren't silly $$$$. 

So much automation is required to get around basic stuff. Come on. 

any news?

I would suggest the following:

The user should be able to activate or deactivate the notification in the profile. This should not be done in every ticket but globally. Like there is an option to 'subscribe' to all notifications when a comment was added. 

Please consider to add this feature. This would increase the usability.

Please.

Please.

https://getsupport.atlassian.com/browse/JST-895219

Hi, 

By using Jira we will try to exclude the manual emails, so all the emails can manage from JIRA, so customers want each notification to each member of the organization. Please take this on a priority basis as this affects our customers.

I opened a support case because of this behavior, because I never imagined something like this was planned behavior.

I mean... WHY sending ONE message about a ticket, but no more. All or nothing would be possible thoughts, but one?

Come on, guys! This can't be so difficult to change. Just do it!

What a deception! It was on of main requirements selection of a Service Desk tool and now I have this surprise that the "notification to all participants" requires that each user have an action for every ticket?????? 

Due to the numerous limitations of the system, our structure requires the creation of several organizations for a single client, additionally, our clients have many contacts in each organization, many of them work on larger projects in a team (many clients treat the organization as a kind of team within a larger structure,. Which is a normal consequence of other system limitations), so they want to be kept informed about the progress of work . As mentioned many times above, this feature should be available by default

Wow, Atlassian... a ticket created in 2016 which should've been a "BASIC" default configuration option is still "gathering interest"?

Maybe I should ask the 1,500 employees from the company to all vote for this feature. Would that raise its priority?

When a customer raises a request, I want to set everyone in that organization as request participants. Even via Automation Rules that would be fine but Editing request participants via automation rules doe not allow you to copy values from organizations, yet it allows copy from CAB Managers, Approvers etc. Please add Organisations to that list.

Thank you

It's been exactly 6 months since I posted about crying myself to sleep every night knowing that this isn't default behavior in JSD. I've continued to cry to the point where I'm having issues with my tear ducts. I've generated multiple gallons of tears. I'm heartbroken. Pls fix ASAP.

We currently use organizations to act as a proxy for our internal company mailing lists to ensure visibility and transparency to certain teams about bugs, features, and other types of important requests. This solution also allows the project admins to maintain the list of users within the organization without admin input.

However, if we ever have to send out a notification beyond what is out-of-the-box using the automation, this solution falls apart because we cannot use organizations within the automation product. This then requires us to then maintain both an organization and group  so we can have visibility and communication. It compromises the team's ability to be self-empowered and ensures that records and notifications are bound to be out of date.

Created on 2016? Really?

I was looking for a way to enable notifications for customers in organizations. I wondered what I set up wrong, but seeing this is not even a feature of the Jira Service Desk is just shocking! And I am sad to say it is not the only shock I'm facing with setting up Jira Service Desk, I am surprised with the number of basic features that are missing.  

That'd be great if this feature is manageable by the sysadmins. 

Asana can definitely do this.

I'm not related to any of this people and I don't hear anybody crying, but I'm tired of receiving updates about this ticket which don't include the message "We've implemented this". Please guys, add this feature.

I'm sure Asana can do this... just sayin 🤷‍♂️

Hey I installed the lighting in the basement and can confirm that I could hear the crying all the way down into the basement. I do not live in the neighborhood but I'm a concerned citizen and would like for someone with authority to fix this ASAP!

PS. Post-2020 this seems like the humane thing to do!

I'm a recent father and I don't want my child to grow up in a world where she can't do this. Please add this as a feature

The only notifications I receive by default are Michael's cries, and I have no way of opting out.  Adding this feature would greatly improve my well-being and workflow.

Hello I am a friend of a friend who is friends with someone who lives with the therapist, and they said this is the most important feature in existence. 

Hello I am a therapist in the local area. All of my patients are complaining about this and are experiencing negative cognitive affects. Basically it's lobotomies for a handful of engineers or we fix this sometime soonish.

Hey! I live in Christopher's basement and thus can also hear the cries. Please help add this functionality

Hi I work remote, but I can still hear Michael's cries from a distance far away.

Hi I live a few neighborhoods over, but the crying is really loud and it's scaring my dog. Please help and add this functionality. 

Hi I'm Matt's neighbor, and by implication also Michael's neighbor. Can confirm there is sobbing.  Please consider easing his pain.

Hi I'm Michael's neighbor and I have to listen to him cry himself to sleep every night. Please add this.

I cry myself to sleep every night knowing this isn't default behavior in JSD.

This was first raised over 4 years ago - still in the  'Gathering Interest' status with no ETA. Please could you update us on plans for addressing this. Thanks

Why such a critical feature is missing??

This could look simple but quite important, can you guys just make it happen or add an option for admins to do so? thanks!

This is open from 2016. It is critical for some of your clients. When can we expect it?

I can see this request is open since 2016 however, for us, this is a critical function that is missing.  When can we expect this very simple feature to be enabled?

When can we expect this to be reviewed / developed. It is a critical part of the platform that is causing additional admin for my team and our clients - and isn't a logical user experience.

Is this feature available yet? this is major limitation!!

We would benefit from this as well

We need this, too... Is there a plan when this is getting implemented?

This is very critical as my clients have reported that they need to explicitly opt in for every issue there team members are raising. Even if they are part of the same organisation, still they need to opt for the notifications.

This is really a no-go for ServiceDesk.

Users should be notified by default, or have it as a global configuration.

I think that's not a simple suggestion, na it's a very important limitation for our customers.

We really need this option too. Please add this change.

Our customers prefer to be notified with all changes by default. I also need this option. Please fix it.