GitLab issues

All tasks are tracked by GitLab issues. Each issue carries a status that shows where it stands in the workflow.

Statuses workflow

  1. Open — the issue has been reported or requested, but it is not planned or prioritized yet. Anyone can create an issue; the squad lead triages it.
  2. Awaiting specifications — the design, functional and technical specifications still have to be written before work can start. This status is skipped when the issue is already clear enough.
  3. Awaiting development — the issue is fully specified (product-wise and technically) and ready to be picked up.
  4. In development — the issue is being studied (researched), developed, and goes through the code review process.
  5. On hold — the work is blocked, waiting on someone else (for example a customer or another team), or the issue failed validation and needs more work. Once the developer is ready to take it on, the issue goes back to In development.
  6. In validation — an artifact (build or staging environment) is available and the issue is being tested.
  7. Awaiting deployment — the issue is validated; a new version of the software has to be tagged and released to end users.
  8. Done — the issue is finished and deployed.

An issue can also be closed without being done:

  • Won't do — the issue is closed without being done.
  • Duplicate — the issue is closed because another one already covers it.
graph TD
    S0[Open] --> S1[Awaiting specifications]
    S0 --> S2[Awaiting development]
    S1 -->|design, functional, tech| S2
    S2 --> S3[In development]
    S3 <--> S4[On hold]
    S3 --> S5[In validation]
    S5 -->|needs work| S4
    S5 --> S6[Awaiting deployment]
    S6 -->|release| S7[Done]