slack
slack copied to clipboard
integrations
Detailed filtering and/or multiple label functionality
Is your feature request related to a problem? Please describe. I'm unable to track what I specifically need with the existing one-label filter. I either can't get enough information, or I get a flood of spam information to catch all the things I need.
Describe the solution you'd like I'd love to be able set certain conditions with multiple labels for filtering. For example: I want all PRs for my/repository with the labels cool AND urgent... requiring both. I want all PRs for my/repo2 with the labels rad OR tubular... only needing to satisfy one of these label requirements. I want all PRs for my/repo3 EXCEPT those with the label not-my-team.
It would be especially helpful to filter each feature individually as well, rather than one monolith for the whole repo.
I'd also like to turn off closed PR notifications, and only see open PRs if reviews are requested.
Describe alternatives you've considered I think more slash commands could help the situation, only retrieving some of the specific information via parameters that allow for the filtering functionality above, when needed.
@brennaharden Thanks for your feedback. Yes, we have plans to work on the providing advanced filter capabilities. We will try to pick this up next quarter.
+1, especially on the "I want all PRs for my/repo3 EXCEPT those with the label not-my-team" part
I'd also really love this feature. Is there any expected timeline for this feature?
Saw that on Stack Overflow in 2019 they recommend just building it yourself. https://stackoverflow.com/questions/44308519/slack-github-integration-send-messages-by-labels
Also saw that in the past it's been blocked as a PR https://github.com/integrations/slack/pull/797
And original issue: https://github.com/integrations/slack/issues/384 with lots of discussion
Same same -- would be great for filtering out noise for those of us working in mono-repos.
+1, we can't really use this app as we are either overloaded with notifications, either we don't receive all as we can all set one label.
+1, in an engineering team of 50+, subscribing to a single label leads to a lot of noise. Having the capability to consume a combination of filters would really sort the scene.
UGH. I hate that I have to set up each idiot repo with the same settings, over and over and over. And I can't filter messages by author/etc. Why can't I just have a workflow file in my github actions that....wait... maybe that's what I need to do.
But wait... I need different notifications than my team. So do I customize a workflow just for myself? Sigh.
