Clarify the necessity of creating Feature Flag Rollout issue
What does this MR do?
Today, our Feature Flags for Developments recommends to create a new issue for Feature Flag Roll Out:
A development feature flag should have a rollout issue, ideally created using the Feature Flag Roll Out template.
However, creating a new issue for rollout is not ideal in some cases, as the information is isolated from the original/feature issue and it's less transparent for anyone (especially, non-DRIs, such as customers, users and managers) who are subscribing the original issue for tracking the progress. For example, this user was confused that why a feature behavior was suddenly changed until employee explained that the feature was temporarily disabled due to an unexpected bug.
In general, we should use the original/feature issue as single source of truth that is a single place to provide all the information regarding the feature. This MR clarifies the point.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team