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

[FEATURE] TEAM sending Slack messages to Slack channels instead of people #351

Open
ccioltan opened this issue Jan 20, 2025 · 4 comments
Open

Comments

@ccioltan
Copy link

Hello,

We are in a great need of having the TEAM Slack configuration to send messages/updates to a specific Slack channel instead of directly to persons. Can you please help with this?

@ccioltan ccioltan changed the title [FEATURE] Slack sending messages to Slack channels instead of people [FEATURE] TEAM sending Slack messages to Slack channels instead of people Jan 20, 2025
@Dragos08
Copy link

Hello,
This would be a big plus indeed. Me and my team are also enabling TEAM and we'd like it to be able to send Slack notifications directly to slack channels instead of DM.

Hope you guys take this into consideration! 🙏

@AlDawoode
Copy link

AlDawoode commented Jan 20, 2025

In my case, I’d need it to support Microsoft Teams. but i did implemente it 😅
Maybe it's time to contribute.

@tawoyinfa
Copy link
Contributor

@AlDawoode I will be happy to review and merge if you contribute this back.

@AlDawoode
Copy link

AlDawoode commented Jan 21, 2025

@tawoyinfa
First of all, I’m unable to open a pull request, so I’m unsure how to contribute this change back to the repository.

Secondly, when I implemented the Microsoft Teams notifications feature, I replaced the SlackNotification functionality with it. But it is not a big problem I can have the two functionality SlackNotificaiton and Microsoft teams notification.

Additionally, my implementation only sends notifications to the Teams channel when someone submits a request via Teams. It does not send notifications when a request is closed or approved/denied.

Image

This decision was intentional to reduce notification noise and ensure that only the most relevant updates are communicated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants