diff options
Diffstat (limited to '.gitlab/issue_templates/Feature Flag Roll Out.md')
| -rw-r--r-- | .gitlab/issue_templates/Feature Flag Roll Out.md | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/.gitlab/issue_templates/Feature Flag Roll Out.md b/.gitlab/issue_templates/Feature Flag Roll Out.md index f3830a5cc10..a9f96a61d29 100644 --- a/.gitlab/issue_templates/Feature Flag Roll Out.md +++ b/.gitlab/issue_templates/Feature Flag Roll Out.md @@ -82,6 +82,7 @@ _Consider adding links to check for Sentry errors, Production logs for 5xx, 302s ### Preparation before global rollout +- [ ] Set a milestone to the rollout issue to signal for enabling and removing the feature flag when it is stable. - [ ] 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. @@ -167,4 +168,11 @@ You can either [create a follow-up issue for Feature Flag Cleanup](https://gitla /chatops run feature set <feature-flag-name> false ``` -/label ~"feature flag" ~"type::feature" ~"feature::addition" +<!-- 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. --> + +/label ~group:: +/label ~"feature flag" +/assign me +/due in 1 month |