Exclude certain groups from notification by email

Options
Harald Hotz-Behofsits
Harald Hotz-Behofsits Member Posts: 157
edited September 2016 in
We have an organization wide group everyone, providing read access to most projects. This enables the project managers to maintain access right inside the project.

At changing items it is possible when notify checkbox is checked to send emails about that change. I would like to have means to limit that feature.

Rationale:
By accident a user selected everyone to get informed. The result was a mail flood to more than 500 users, many of them clicked at the same time the link, using all floating licences just in seconds.

Either the ability to exclude certain groups from being selectable in notifications or havin g the ability to switch that all, would be welcome to avoid that in future.

Comments

  • [Deleted User]
    [Deleted User] Posts: 911
    edited September 2016
    Options
    Harald, yes, I agree this would be nice to have. I wish the ability to notify was more controlled from the admin/project manager perspective as well as from the end-user perspective. Thanks for bringing this up.
  • [Deleted User]
    [Deleted User] Posts: 1
    Options
    We would be interested in turning off or excluding groups as well.  A global flag to disable Notify All would be great as well.
  • Anja Airasvirta
    Anja Airasvirta Member Posts: 53
    edited October 2018
    Options
    Now user is able to select any of the organization level user group and those project specific user groups where he/she is member.  Problem is here that user might send notification as "spam" e-mail for whole Jama user-base who just needs the visibility to this project. This is not a good thing.
    It would be better if the notification can be send only for the project specific groups.  At least there could be a possibility to select if the organization level groups are available for all users or only the organization admins to be used for notification purposes.
    Anja
    [Country]
  • Ryan Dill
    Ryan Dill Member Posts: 57
    edited August 2021
    Options

    Like Harald, we also have a number of larger organization-wide groups set up for defaulting project permissions.

    We just encountered a similar scenario where a new user made a change, didn't notice the auto-selected "Notify" checkbox, and mistakenly interpreted the next (notify) screen as "what group does your change pertain to" -- selecting an org-level group without realizing this would email all 1000+ users in the group. As in Harald's case, the result was a storm of email, a mass attempt by emailed users to log into Jama to see what the change was, and exhaustion of floating licenses.

    Being able to block certain groups from notification at the org admin level would be extremely useful.

    Alternatively, would it be useful to have an org-configurable threshold for notifications, beyond which an "Are you sure" prompt would be raised to inform the user of the large number of emails that are about to be sent out, so that they have the chance to refine their notification settings before pulling the trigger?

    Ryan Dill
  • Decoteau Wilkerson
    Decoteau Wilkerson Jama Staff, Data Exchange, Moderator, Automotive Solution, Medical Devices & Life Sciences Solution, Robotics Solution, Airborne Systems, Jama Connect Interchange™ (JCI), Jama Validation Kit (JVK) + Functional Safety Kit (FSK) Posts: 48
    edited August 2021
    Options
    Hi Ryan, 

    I was curious to see whether anyone's filed an Ideation Card for this and found this Idea: 
    Enforce at project / org level Save & Notify for all edits

    It sounds like the ask there is similar to your post here. If you're interested in participating, could you like/comment on that card? That will give our Product team better context for this request.
    Decoteau Wilkerson
    Content Marketing Specialist
    Jama Software
    Oregon
  • Robena Sukhu
    Robena Sukhu Member Posts: 23
    edited August 2021
    Options

    + 1

     

    Robena Sukhu

    Sun Life Financial

     

    ___________________________________________________________________________

    This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary, confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately.

    Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. Si ce message vous a été transmis par erreur, veuillez en informer l'expéditeur et le supprimer immédiatement.

    Being able to block certain groups from notification at the org admin level would be extremely useful.

    Alternatively, would it be useful to have an org-configurable threshold for notifications, beyond which an "Are you sure" prompt would be raised to inform the user of the large number of emails that are about to be sent out, so that they have the chance to refine their notification settings before pulling the trigger?

    Robena Sukhu
    Sun Life Financial
    ON
    416-496-5456

Categories