<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=196878) </details> <!--IssueSummary end--> ### Problem to solve <!-- What problem do we 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 <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> * [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager) ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> * 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 <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further help: https://about.gitlab.com/handbook/engineering/quality/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> * 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? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> * Be definition, in this case, it's an exec, so ~"GitLab Ultimate", but I'm sure other buyers also have similar needs. ### Links / references