microsoft-teams
microsoft-teams copied to clipboard
How can each team member subscribe to pull request notifications?
Is there a way that every team member can subscribe to notifications when he/she has been assigned to a pull request? So far I only managed to add notifications to a whole channel. The chatbot doesn't seem to offer that functionality?
@yss14 Thanks for your feedback. Subscriptions are at channel level. We have few features in our backlog that can address this scenario. As part of public beta we are introducing support for filtering your subscriptions on Labels. This can help in getting notifications for only relevant subscriptions. Post beta, we have plans to introduce @mentions support. With this a user will notified in Teams when added to a pull request or an issue. If you are interested, we can have a call and I can share our plans, experience and timelines.
Post beta, we have plans to introduce @mentions support. With this a user will notified in Teams when added to a pull request or an issue.
This sounds great! Thank you very much for the detailed information.
This will be part of personal app experience we will be working on this quarter. Keeping this issue open for us to track.
Can't seem to get subscriptions to work at channel level
Channel level subscriptions require users to be Organization Admins, which isn't practical in my company (or any large company) I imagine. I opened a ticket #105 about that issue.
Being able to subscribe to PRs individually would solve my use-case (as long as I don't have to be an org admin to subscribe!)
This is a must-have feature for my organization. The Slack integration does this flawlessly where you can define your "real-time" alerts (like only notify me when I get assigned to a pull request). It would be amazing to receive the same real-time notifications in Teams.
GitHub settings to enable real-time alerts to Slack Notification (under the Settings -> Scheduled Reminders -> org):
Please enable this functionality.
The workaround is to subscribe to each repo we care about, but that is unfeasible for my organization since we have 100+ repos we could be reviewers for.
Related to #100 and #121. I created #162 because my use case might be slightly different than what is discussed here, but still related.
