Skip to content

馃煝 Customizable status - Feedback

Move beyond the basic open/closed system with configurable status that lets you track work items through your team's actual workflow stages. Instead of relying on labels to indicate whether an issue or task is "In Progress," "Blocked," or "Ready for Testing," you can now define custom statuses that accurately reflect your process.

With configurable status, you can:

  • Define custom workflows with statuses like "In Progress," "In Review," "Blocked," or "Ready for Testing" that match your team's actual process.
  • Replace workflow labels with proper statuses that are easier to find, update, and report on.
  • Clarify completion outcomes using "Done" or "Canceled" category statuses to indicate whether work was actually completed or abandoned.
  • Filter and report accurately on work item status for better project insights.
  • Use status in issue boards as board lists, with automatic status updates when you move items between columns.
  • Bulk update status across multiple work items for efficient workflow management.
  • Track dependencies with status visibility for linked work items.
  • Update by using quick actions in comments for seamless workflow integration.

Status automatically syncs with GitLab's open/closed system: items with "Done" or "Canceled" category statuses are automatically closed, while others remain open. New issues and tasks receive appropriate default statuses upon creation.

Custom statuses are configured for the top-level group, ensuring consistent workflow definitions across all projects and subgroups in your namespace while maintaining organizational flexibility.

馃摉 Learn more in the Docs

馃摴 Watch a video walkthrough

Related work in our upcoming roadmap

  • Expand coverage to epics (Epic)
  • Enable type-based workflows for more specificity (Epic)
Edited by Marc Saleiko