Skip to content

VSA - tracking the new Workflow Status

Overview

Customizable work item statuses provide a foundation for building a more robust work item lifecycle management solution, and enable teams to mark work items as done or cancelled. This will help large companies need custom workflows as part of their issue management. An example is that a team needs to ensure every single issue goes through exactly these stages: "To Do" > "In Dev" > "In QA" > "Code review" > "UAT" > "Ready for release" > "Post-production check". Work Item Statuses are intended to replace the use of status labels, a common practice in many teams using GitLab including our own workflowstart scoped labels.

Default statuses

  • Default statuses - Defaults allow users to get started with status without having to set anything up. In the first iteration only defaults will be available; once configuration is added users can change or remove most defaults.
  • Default statuses will be: To do, In progress, Done, Won't do, Duplicate

Custom statuses

  • Custom statuses are intended to enable teams to represent their workflow through statuses and replace the use of status labels, a common practice in many teams using GitLab including our own workflowstart scoped labels.

Problem

Value stream analytics needs to track OOTB the new workflow state.

Proposal

  • Create a separate dropdown for Type (e.g. Issue, Merge request)
  • Clean up the start and end events drop downs to support groupings
  • Add "Statuses" as options to select from
Current Proposal (start) Proposal (end)
Current Proposal_-_Start_event Proposal_-_End_event
Edited by Libor Vanc