Subscribe to label => post to Slack
Problem to solve
We have a label CEO Interest which we put on issues and epics to indicate that Sid, our CEO has an interest in this item, and any substantial changes to should be communicated to him in the #ceo Slack channel. This involves manual effort, and it shouldn't.
Intended users
Further details
- Sid should be able to subscribe to the CEO Interest label and automatically get what he wants.
- We should be able to send label notifications to a Slack channel.
- Not all issue/epic events should be communicated. e.g. Sid doesn't care about every comment; he wants to know key things like if the milestone changes, or the issue is closed/moved.
- Some additional information may be needed, such as why an issue has changed milestone. Currently that information is supposed to be communicated as a comment at the time of changing the milestone, but is also manually typed into the Slack message. We should have some way to not only provide that why, but also understand that it's information of a different kind. e.g. ask "why" when changing the milestone and construct a comment from that information, but also store it uniquely; provide notification filters to include/exclude that information.
- We could, of course, generalize these needs by allowing more customizable notification feeds and Slack integration.
Proposal
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
- Increased efficiency by removing manual actions, greater compliance with notifications, greater adoption of notifications and Slack integration, less (or no) manual Slack messages.
What is the type of buyer?
- Be definition, in this case, it's an exec, so GitLab Ultimate, but I'm sure other buyers also have similar needs.