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

Make notification logic and glue to services #1

Open
falkecarlsen opened this issue Oct 9, 2021 · 1 comment
Open

Make notification logic and glue to services #1

falkecarlsen opened this issue Oct 9, 2021 · 1 comment

Comments

@falkecarlsen
Copy link
Member

Would be great to have both Slack and mail notification-channels and a flow for issues that needs action:

  1. Send msg to Slack-channel for coffee-machine guys
  2. If no user has reacted to msg with 👍 within timeframe, send also mail to treo-mailinglist
  3. If user has reacted to msg with 👍 does not also react with :fixd:/:fritfit: within timeframe, also send mail.

This is less spammy than just always mails, and enables some form of 'assignment' of issues to solve for the coffee-machine guys.

@hrjakobsen
Copy link
Member

I've implemented almost exactly this workflow previously with Slack. I used the blocks api buttons to trigger a callback to my service that could then do further processing. In this callback you can update the message (remove buttons etc). It works quite well.

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

2 participants