Implement Incident Follow-up Workflow
## Overview
This epic covers the implementation of a standardized workflow for incident follow-up issues, as documented in the [Incident Follow Up Issues handbook page](https://handbook.gitlab.com/handbook/engineering/infrastructure/incident-management/incident-follow-ups/). The implementation includes setting up default issue locations, defining incident lead responsibilities, establishing triage processes, enforcing appropriate labeling, and configuring incident.io integration.
## Background
Currently, follow-up items from incidents (especially those created via incident.io) often lack clear ownership and may fall through the cracks due to inconsistent processes. We need to implement a standardized workflow that ensures proper tracking and resolution of incident follow-up items across both GitLab.com and Dedicated teams.
## Goals
- Create and configure default issue repositories for incident follow-ups
- Document and train incident leads on their responsibilities
- Implement a consistent triage process for both GitLab.com and Dedicated teams
- Establish proper labeling standards
- Configure incident.io to use the new issue queues
- Ensure no follow-up items are missed through regular reviews
## Success Criteria
1. All incident follow-up items are properly tracked in the appropriate repositories
2. Incident leads consistently follow the documented process for managing follow-up items
3. Follow-up issues contain sufficient context and clear acceptance criteria
4. Weekly triage meetings successfully identify and address any untriaged items
5. Engineering teams are aware of their infradev issues and actively working to resolve them
6. The number of "lost" follow-up items is reduced to zero
## Related Issues and Documents
- [Define new process for follow-up items from incident.io (#26582)](https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/issues/26582)
- [Incident Follow Up Issues Handbook Page](https://handbook.gitlab.com/handbook/engineering/infrastructure/incident-management/incident-follow-ups/)
- [Engineering Workflow - InfraDev](https://handbook.gitlab.com/handbook/engineering/workflow/#infradev)
- [Product Processes - InfraDev](https://handbook.gitlab.com/handbook/product/product-processes/#infradev)
- [Incident Management - Corrective Actions](https://handbook.gitlab.com/handbook/engineering/infrastructure/incident-management/#corrective-actions)
## Issue Admin
```
/epic &1583
/labels ~"team::Ops" ~"group::Production Engineering" ~Department::Infrastructure ~"Sub-Department::SaaS Platforms" ~"Reliability::P2" ~"workflow-infra::Proposal"
```
epic