<!-- Title suggestion: [Feature flag] Enable description of feature --> In %"15.8" the integrations group in the Manage stage will be completing work for the Slack Application Integration. They will be making updates to the App Home, the Slack Landing Page, and the GitLab Landing page. These are the final touches in preparation for releasing our consolidated Slack application. ## Summary This issue is to rollout [Slack Application integration with the support for Slack notifications feature](https://gitlab.com/groups/gitlab-org/-/epics/8670) on production, that is currently behind the `integration_slack_app_notifications ` feature flag. Currently, "Slack notifications" and "Slack Application" are two different integrations. The feature introduced here consolidates these and moves the "Slack notifications" into the "Slack Application" integration. ## Owners - Team: Manage Integrations Group - Most appropriate slack channel to reach out to: `#g_manage_integrations` - Best individual to reach out to: @.luke - PM: @m_frankiewicz / @g.hickman ## Stakeholders <!-- Are there any other stages or teams involved that need to be kept in the loop? - Name of a PM - The Support Team - The Delivery Team --> @abellucci ## Expectations ### What are we expecting to happen? The Slack Notifications to become part of the Slack Application integration. At the same time, it should be acceptable to keep the Slack Notifications as a separate integration entry for some time to give users time to get used to the new settings location. ### When is the feature viable? The feature is supposed to be viable immediately after the feature flag enablement. ### What might happen if this goes wrong? The flag should be turned off. Keeping the Slack Notifications as a separate integrations entry will help reduce the risks. ### What can we monitor to detect problems with this? - New [Sentry errors](https://sentry.gitlab.net/gitlab/gitlabcom/?query=is%3Aunresolved+feature_category%3Aintegrations) related to the GitLab Slack application. - [Kibana errors](https://log.gprd.gitlab.net/goto/6141aa00-5b09-11ed-8d37-e9a2f393ea2a) for `Integrations::ExecuteWorker` related to the GitLab Slack application. ### What can we check for monitoring production after rollouts? See above. ## Rollout Steps ### Rollout on non-production environments - Ensure that the feature MRs have been deployed to non-production environments. - [x] `/chatops run auto_deploy status <merge-commit-of-your-feature>` - [x] Enable the feature globally on non-production environments. - [x] `/chatops run feature set integration_slack_app_notifications true --dev --staging --staging-ref` - [x] Verify that the feature works as expected. Posting the QA result in this issue is preferable. The best environment to validate the feature in is [staging-canary](https://about.gitlab.com/handbook/engineering/infrastructure/environments/#staging-canary) as this is the first environment deployed to. Note you will need to make sure you are configured to use canary as outlined [here](https://about.gitlab.com/handbook/engineering/infrastructure/environments/canary-stage/) when accessing the staging environment in order to make sure you are testing appropriately. ### Specific rollout on production - Ensure that the feature MRs have been deployed to both production and canary. - [ ] `/chatops run auto_deploy status <merge-commit-of-your-feature>` - If you're using [project-actor](https://docs.gitlab.com/ee/development/feature_flags/#feature-actors), you must enable the feature on these entries: - [ ] `/chatops run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss,gitlab-com/www-gitlab-com integration_slack_app_notifications true` - If you're using [group-actor](https://docs.gitlab.com/ee/development/feature_flags/#feature-actors), you must enable the feature on these entries: - [ ] `/chatops run feature set --group=gitlab-org,gitlab-com integration_slack_app_notifications true` - If you're using [user-actor](https://docs.gitlab.com/ee/development/feature_flags/#feature-actors), you must enable the feature on these entries: - [ ] `/chatops run feature set --user=<your-username> integration_slack_app_notifications true` - [ ] Verify that the feature works on the specific entries. Posting the QA result in this issue is preferable. ### Preparation before global rollout - [x] Set a milestone to the rollout issue to signal for enabling and removing the feature flag when it is stable. - [x] Check if the feature flag change needs to be accompanied with a [change management issue](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#feature-flags-and-the-change-management-process). Cross link the issue here if it does. - [x] Ensure that you or a representative in development can be available for at least 2 hours after feature flag updates in production. If a different developer will be covering, or an exception is needed, please inform the oncall SRE by using the `@sre-oncall` Slack alias. - [x] Ensure that documentation has been updated ([More info](https://docs.gitlab.com/ee/development/documentation/feature_flags.html#features-that-became-enabled-by-default)). - [ ] Announce on [the feature issue](ISSUE LINK) an estimated time this will be enabled on GitLab.com. - [x] Ensure that any breaking changes have been announced following the [release post process](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-removals-and-breaking-changes) to ensure GitLab customers are aware. - [x] Notify `#support_gitlab-com` and your team channel ([more guidance when this is necessary in the dev docs](https://docs.gitlab.com/ee/development/feature_flags/controls.html#communicate-the-change)). ### Global rollout on production - [x] Click the Publish button to publish our GitLab Slack app which was submitted for review in https://gitlab.com/gitlab-org/gitlab/-/issues/384226 ([see docs](https://gitlab.com/gitlab-org/manage/integrations/team/-/blob/main/integrations/slack.md#5-once-approved-publish-the-app)) - [x] Assign the ~documentation MR https://gitlab.com/gitlab-org/gitlab/-/merge_requests/104639 to a Technical Writer to have it be merged. For visibility, all `/chatops` commands that target production should be executed in the `#production` slack channel and cross-posted (with the command results) to the responsible team's slack channel (`#g_TEAM_NAME`). - [ ] [Incrementally roll out](https://docs.gitlab.com/ee/development/feature_flags/controls.html#process) the feature. - If the feature flag in code has [an actor](https://docs.gitlab.com/ee/development/feature_flags/#feature-actors), perform **actor-based** rollout. - [ ] `/chatops run feature set integration_slack_app_notifications <rollout-percentage> --actors` - If the feature flag in code does **NOT** have [an actor](https://docs.gitlab.com/ee/development/feature_flags/#feature-actors), perform time-based rollout (**random** rollout). - [ ] `/chatops run feature set integration_slack_app_notifications <rollout-percentage> --random` - Enable the feature globally on production environment. - [x] `/chatops run feature set integration_slack_app_notifications true` - [x] Announce on [the feature issue](ISSUE LINK) that the feature has been globally enabled. - [ ] Wait for [at least one day for the verification term](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#including-a-feature-behind-feature-flag-in-the-final-release). ### Release the feature After the feature has been [deemed stable](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#including-a-feature-behind-feature-flag-in-the-final-release), the [clean up](https://docs.gitlab.com/ee/development/feature_flags/controls.html#cleaning-up) should be done as soon as possible to permanently enable the feature and reduce complexity in the codebase. You can either [create a follow-up issue for Feature Flag Cleanup](https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Feature%20Flag%20Cleanup) or use the checklist below in this same issue. <!-- The checklist here is to help stakeholders keep track of the feature flag status --> - [ ] Create a merge request to remove `integration_slack_app_notifications` feature flag. Ask for review and merge it. - [ ] Remove all references to the feature flag from the codebase. - [ ] Remove the YAML definitions for the feature from the repository. - [ ] Create [a changelog entry](https://docs.gitlab.com/ee/development/feature_flags/#changelog). - [ ] Ensure that the cleanup MR has been included in the release package. If the merge request was deployed before [the monthly release was tagged](https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-1), the feature can be officially announced in a release blog post. - [ ] `/chatops run release check <merge-request-url> <milestone>` - [ ] Close [the feature issue](ISSUE LINK) to indicate the feature will be released in the current milestone. - [ ] If not already done, clean up the feature flag from all environments by running these chatops command in `#production` channel: - [ ] `/chatops run feature delete integration_slack_app_notifications --dev --staging --staging-ref --production` - [ ] Close this rollout issue. ## Rollback Steps - [ ] This feature can be disabled by running the following Chatops command: ``` /chatops run feature set integration_slack_app_notifications false ``` <!-- A feature flag can also be used for rolling out a bug fix or a maintenance work. In this scenario, labels must be related to it, for example; ~"type::feature", ~"type::bug" or ~"type::maintenance". Please use /copy_metadata to copy the labels from the issue you're rolling out. --> ### Availability & Testing Slack notifications are a good instance of behavior to test e2e. Follow up with https://gitlab.com/gitlab-org/gitlab/-/merge_requests/100448 <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? 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? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the Quality Engineering quad planning and test planning processes and reach out to your counterpart Software Engineer in Test for assistance. Quad Planning: https://about.gitlab.com/handbook/engineering/quality/quality-engineering/quad-planning Test Planning: https://about.gitlab.com/handbook/engineering/quality/quality-engineering/test-engineering/#test-planning -->