Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team notifications being sent despite disabled in Team Settings #34499

Closed
1 task done
programarivm opened this issue Sep 5, 2024 · 3 comments
Closed
1 task done

Team notifications being sent despite disabled in Team Settings #34499

programarivm opened this issue Sep 5, 2024 · 3 comments
Labels
content This issue or pull request belongs to the Docs Content team organizations Content related to organizations

Comments

@programarivm
Copy link

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/organizations/organizing-members-into-teams/configuring-team-notifications

https://github.blog/news-insights/introducing-team-mentions/

What part(s) of the article would you like to see updated?

Hi there,

ChesslaBlab is a GitHub organization with over 1,000 people.

We're using team mentions once a month to send a notification to all members through GitHub Discussions, however, it seems as if everone is being notified when someone writes a new comment in the discussion.

Is it documented how to disable notifications after the initial one has been sent?

See https://github.com/orgs/chesslablab/discussions/435

Is this a bug or a feature?

Thanks for the help,

Additional information

No response

@programarivm programarivm added the content This issue or pull request belongs to the Docs Content team label Sep 5, 2024
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Sep 5, 2024
@jsoref
Copy link
Contributor

jsoref commented Sep 5, 2024

I'd personally open a ticket using https://support.github.com/contact/bug-report

I know that the interactions between notifications/subscriptions is quite confusing, so I'd hope that someone from support could identify what's going wrong.

My bet is that the documentation needs to be improved (I'm about to file a bug in this specific area, so I searched before opening it, so I definitely believe there are shortcomings), but it's also not impossible there's something simple that could be done to the ticket (and possibly also to the team configuration)... Offhand, for a team this large I would make it invisible:

https://docs.github.com/en/organizations/organizing-members-into-teams/changing-team-visibility

One thing that I can see that's definitely deficient in this area is that it shows how to mass change team visibility but doesn't explain how to do it per team:

image

@jsoref
Copy link
Contributor

jsoref commented Sep 5, 2024

Note to GitHub staff the (Recommended) suffix should be removed from any team with >20 members for exactly the reasons that caused this ticket to be opened. Instead, Secret should get the (Recommended) tag.

References

@nguyenalex836 nguyenalex836 added organizations Content related to organizations and removed triage Do not begin working on this issue until triaged by the team labels Sep 5, 2024
@nguyenalex836
Copy link
Contributor

@programarivm Thank you for opening an issue! ✨

however, it seems as if everone is being notified when someone writes a new comment in the discussion.
Is it documented how to disable notifications after the initial one has been sent?
Is this a bug or a feature?

It does not look like we currently have documentation on how to disable notifications after the initial notification has been sent, though this may be related to what the expected behavior of these notifications is.

While our Docs team wouldn't be the best group to speak to expected behavior of these notifications, per the guidance from @jsoref, opening a support ticket with the context he provided would the best path toward determining what may be going wrong 💛

If after reaching out to our Support team there are updates that should be made to these docs, please feel free to reopen this issue, and we can work together on updating them!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team organizations Content related to organizations
Projects
None yet
Development

No branches or pull requests

3 participants