Transition to Statuses for Product Development Flow: Feedback & Issues
We're transitioning from workflow labels to statuses as the standard way to track work items through the Product Development Flow. This change affects all teams working in GitLab projects. ## What's changing 1. Use statuses instead of workflow labels to track where work items are in the flow 2. Workflow labels are deprecated and should no longer be used after 2026-02-27 3. Automatic syncing keeps labels and statuses aligned during the transition period 4. Currently live in gitlab-org/gitlab, rolling out to all gitlab-org and gitlab-com projects soon ## Use this issue to - :bug: Report problems using statuses or issues with the transition - :speech_balloon: Share feedback on your experience moving to status-based tracking - :question: Ask questions about statuses, the timeline, or what this means for your workflow - :people_holding_hands: Get advice on moving your issue boards, bookmarks, automations, and team processes to use Statuses - :bulb: Suggest improvements to make the transition smoother ## Related links - Slack announcement - [Product Development Flow handbook update](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/18034) - [triage-ops sync implementation](https://gitlab.com/gitlab-org/quality/triage-ops/-/merge_requests/3673)
issue