[Feature flag] Rollout of `jira_issue_association_on_merge_request`

What

Roll out the :jira_issue_association_on_merge_request feature flag added in &4637.

Owners

• Team: groupcompliance
• Most appropriate slack channel to reach out to: #g_manage_compliance
• Best individual to reach out to: @jiaan @mwoolf @tancnle

Expectations

What are we expecting to happen?

1. A new project-level general setting to show. #268294 (closed)

   

2. When enabled will block a project MR from being merged unless it refers to a Jira issue. !58658 (merged)

   

What might happen if this goes wrong?

This feature is non-destructive. The absolute worst case is that projects with the setting enabled cannot have MRs merged until we rollback.

What can we monitor to detect problems with this?

Test the issue on beta projects.

Beta projects

If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.

• Staging: /compliance-tanuki/fast-project project

• Production: /jiaan/jira-integration-test/ project, gitlab-org/gitlab project

Roll Out Steps

• Enable on staging (/chatops run feature set jira_issue_association_on_merge_request true --staging)
• Test on staging
• Ensure that documentation has been updated - !61719 (merged)
• Enable on GitLab.com for individual groups/projects listed above and verify behaviour (/chatops run feature set --project=jiaan/jira-integration-test jira_issue_association_on_merge_request true)
• [-] Coordinate a time to enable the flag with the SRE oncall and release managers
  • In #production mention @sre-oncall and @release-managers. Once an SRE on call and Release Manager on call confirm, you can proceed with the rollout
  • Not applicable !58480 (merged)
• Announce on the issue an estimated time this will be enabled on GitLab.com
• Enable on GitLab.com by running chatops command in #production (/chatops run feature set jira_issue_association_on_merge_request true)
• Cross post chatops Slack command to #support_gitlab-com (more guidance when this is necessary in the dev docs) and in your team channel
• Announce on the issue that the flag has been enabled
• Remove feature flag and add changelog entry - In a dedicated issue
• After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel - In a dedicated issue

Rollback Steps

• This feature can be disabled by running the following Chatops command:

/chatops run feature set jira_issue_association_on_merge_request false