Document and roll out stale todo auto-resolution
Goal
Document the feature and execute the gradual rollout plan.
Related to #20637 (closed)
Should start after Phase 1d is deployed and stable
Implementation Details
1. User Documentation
Location: doc/user/todos.md
Document which todo types are automatically resolved and which remain pending.
2. API Documentation
Location: doc/api/merge_requests.md
Update merge and close endpoints to mention automatic todo resolution.
3. Changelog Entry
Location: changelogs/unreleased/auto-resolve-mr-todos.yml
Rollout Plan
Week 1: Internal Dogfooding
- Enable for gitlab-org projects
- Gather feedback
- Monitor metrics
Week 2: Beta (10%)
- Enable for 10% of GitLab.com projects
- Monitor for 3-5 days
- Address any issues
Week 3: Gradual Expansion (50% → 100%)
- Increase to 25%, then 50%, then 100%
- Monitor at each stage
Week 4: Feature Flag Cleanup
- Keep as ops flag or remove entirely
Files to Change
-
doc/user/todos.md -
doc/api/merge_requests.md -
changelogs/unreleased/auto-resolve-mr-todos.yml
Acceptance Criteria
-
Documentation clear and accurate -
Rollout completes without incidents -
User feedback positive -
Metrics healthy
Monitoring
- Sidekiq job success rate > 99.9%
- Job duration P95 < 500ms
- Error rate < 0.1%
Estimated Effort: 2 days + 4 weeks rollout