Saltar al contenido principal

Columnas y estados personalizados

La versión en inglés de este artículo es la oficial. El contenido localizado llegará en una próxima actualización.

Every team's workflow is different. LoopGantt lets you customize the Kanban columns to match exactly how your team works — from a simple 3-stage flow to a detailed 7-step process.

Understanding status-based columns

In project management, a workflow is a defined sequence of states that work passes through. Making your workflow explicit has a powerful effect: it forces the team to agree on what "done" means at each stage, which reduces ambiguity and rework.

A well-designed workflow also reveals bottlenecks. If the "In Review" column keeps filling up, reviews are the constraint — and that's something you can fix.

Default columns

LoopGantt ships with four default columns that map to the four task statuses:

ColumnStatus valueMeaning
Not Startednot_startedWork has not begun
In Progressin_progressActively being worked on
On Holdon_holdBlocked or intentionally paused
CompletedcompletedWork is done

Auto-progress on status change

When you move a task to Completed, its progress automatically updates to 100%. Moving to Not Started resets progress to 0%. This keeps the Gantt and Kanban views consistent without manual updating.

How to reorder and manage columns

  1. In Kanban view, click the ⚙ Board settings button.
  2. Drag columns to reorder them. The leftmost column represents the earliest stage; the rightmost is the final "done" state.
  3. Toggle columns on/off to hide stages you don't use.

Working with four statuses

LoopGantt has four fixed statuses: Not Started, In Progress, On Hold, and Completed. This is intentionally lean — most teams don't need seven columns, and fewer statuses mean less bookkeeping.

Tips for getting the most out of four columns:

  • Use On Holdas your "blocked / waiting on review" signal — it's visible to the whole team without a meeting.
  • Use task notes or checklist itemsto track sub-stages like "In Review" within a task that is In Progress.
  • Use task colors to visually distinguish work types (e.g., cyan for design, green for dev) across the board.
Was this article helpful?