[FF] cells_claims_verification_worker_jira_connect_installation -- Claims verification worker for Jira installations

Summary

Roll out the feature currently behind the cells_claims_verification_worker_jira_connect_installation feature flag.

This is the verification worker flag from the claims feature flag hierarchy. Cells::ClaimsVerificationWorker derives the flag name from the model class, so this name is what it checks for JiraConnectInstallation.

The worker scans existing records, creates the claims they are missing and removes the claims that no longer match. Enable the model-specific claims flag first, and let it settle. The worker also honours that flag, so it finds no claimable attributes while the flag is off.

Note

Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. Feature flag controls · Feature flag lifecycle

What could go wrong?

The worker scans the table in batches and calls the Topology Service for each record that needs a claim. The load is therefore proportional to the table size, which is about 109k rows.

The claims flag gates the attributes the worker sees, so enable and settle that flag first. The worker keeps its progress in Redis and stops after a time limit, then reschedules itself.

The flag defaults to off, so the worker skips this model until it is enabled.

Rollout

Run all production /chatops in #production and cross-post the results to #g_import. Background: incremental rollout process, feature actors.

Non-production

/chatops gitlab run feature set cells_claims_verification_worker_jira_connect_installation 50 --actors --dev --pre --staging --staging-ref
/chatops gitlab run feature set cells_claims_verification_worker_jira_connect_installation true --dev --pre --staging --staging-ref

Production — percentage rollout (wait ≥15 min between steps, watch dashboards):

/chatops gitlab run feature set cells_claims_verification_worker_jira_connect_installation <percentage> --actors

Or target specific actors instead:

/chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss cells_claims_verification_worker_jira_connect_installation true
/chatops gitlab run feature set --group=gitlab-org,gitlab-com cells_claims_verification_worker_jira_connect_installation true
/chatops gitlab run feature set --user=jotolo_gl cells_claims_verification_worker_jira_connect_installation true

Before global rollout

Confirm the relevant gotchas before going to 100% — see enabling a feature for GitLab.com:

Cleanup

Remove the flag once deemed stable — see cleaning up. Track it here, or open a follow-up Feature Flag Cleanup issue. Remove the flag and its YAML definition from the codebase, then:

/chatops gitlab run release check https://gitlab.com/gitlab-org/gitlab/-/merge_requests/248948 19.4
/chatops gitlab run feature delete cells_claims_verification_worker_jira_connect_installation --dev --pre --staging --staging-ref --production

Rollback

/chatops gitlab run feature set cells_claims_verification_worker_jira_connect_installation false                                         # production
/chatops gitlab run feature set cells_claims_verification_worker_jira_connect_installation false --dev --pre --staging --staging-ref     # non-production
/chatops gitlab run feature delete cells_claims_verification_worker_jira_connect_installation --dev --pre --staging --staging-ref --production  # remove entirely