Skip to content
GitLab Next
Open
Issue created by Natalia Tepluhina@ntepluhina🌴Maintainer5 of 22 checklist items completed5/22 checklist items

[Feature flag] Rollout of `issue_assignees_widget`

Feature

This feature uses the :issue_assignees_widget feature flag!

Due to the negative feedback and some newly discovered backend issues on assignees widget, we have added a feature flag to display it conditionally.

Owners

  • Team: Plan
  • Most appropriate slack channel to reach out to: #s_plan
  • Best individual to reach out to: @ntepluhina

The Rollout Plan

  • Partial Rollout on GitLab.com with beta projects
  • Rollout on GitLab.com for a certain period (2 weeks)
  • Rollout Feature for everyone as soon as it's ready

Beta Groups/Projects:

  • gitlab-org/gitlab project
  • gitlab-org/gitlab-com groups

Expectations

What are we expecting to happen?

As soon as we fix the new widget, we expect it to fully replace the old assignees component without user complaints.

What might happen if this goes wrong?

If there are any issues with the new widget, the feature flag should be turned off.

Rollout Timeline

Initial Rollout

Preparation Phase

  • Enable on staging (/chatops run feature set issue_assignees_widget true --staging)

  • Test on staging

  • Announce on the issue an estimated time this will be enabled on GitLab.com

Partial Rollout Phase

  • Enable on GitLab.com for individual groups/projects listed above and verify behaviour (/chatops run feature set --project=gitlab-org/gitlab issue_assignees_widget true)

  • Verify behaviour (See Beta Groups) and add details with screenshots as a comment on this issue

Global Availability (More Info) (Please Note that Beta,Alpha and General Availability (GA) are handled on a product level and not the feature-flag)

  • Coordinate a time to enable the flag with #production and #g_delivery on slack.

  • Announce on the issue an estimated time this will be enabled on GitLab.com

  • Make the feature flag enabled by default i.e. Change default_enabled to true

  • Enable on GitLab.com by running chatops command in #production (/chatops run feature set feature_name true)

  • Announce on the issue that the flag has been enabled

  • Cross post chatops slack command to #support_gitlab-com (more guidance when this is necessary in the dev docs) and in your team channel

Cleanup

This is an important phase, that should be either done in the next Milestone or as soon as possible. For the cleanup phase, please follow our documentation on how to clean up the feature flag.

  • Announce on the issue that the flag has been enabled

  • Remove :issue_assignees_widget feature flag

    • Remove all references to the feature flag from the codebase
    • Remove the YAML definitions for the feature from the repository
    • Create a Changelog Entry

  • Clean up the feature flag from all environments by running this chatops command in #production channel /chatops run feature delete issue_assignees_widget.

Final Step

  • Close this rollout issue for the feature flag after the feature flag is removed from the codebase.

Rollback Steps

  • This feature can be disabled by running the following Chatops command:
/chatops run feature set --project=gitlab-org/gitlab issue_assignees_widget false
Edited by Natalia Tepluhina