Skip to documentation
Log in
Browse documentation

Teams and workflows

Statuses, labels and automatic archiving

Customise a team workflow with status groups, reusable labels and an archive policy.

Last updated July 28, 2026

Status groups

Every status belongs to one of four groups:

  • Inactive for ideas, requests and work not ready to begin.
  • To do for planned work that can be started.
  • In progress for work currently underway.
  • Done for completed work.

The group gives Limin a stable meaning even when teams use different status names. It powers system views, status-group filters, completion dates and resolution-note behaviour.

Moving issues into or out of a Done group status also updates their completion state.

Add and reorder statuses

Open Settings → Teams → [team] → Issue statuses. Add a status inside the appropriate group, then move statuses up or down to set their order.

The order controls how columns and status choices appear. Statuses can be reordered within a group but do not change group through reordering.

Use names that describe a meaningful stage. A developer workflow might use Ready, In development, In review, QA and Done.

Delete a status safely

If no issues use a status, it can be deleted directly. If issues still use it, Limin asks you to choose another status first and moves those issues as part of the operation.

Create and manage labels

Labels are team-specific tags used to classify issues. From the Labels section of team settings, you can create, rename and delete them.

Deleting a label removes it from the issues that use it but does not delete those issues. Limin shows the affected issue count before confirmation.

Use a small, consistent label vocabulary. Priorities and statuses already describe urgency and progress, so labels work best for categories such as Bug, Design, Maintenance or a technical area.

Configure automatic archiving

Archived issues remain accessible and read-only. They retain their labels and status at the time of archiving, even if those labels or statuses are later deleted.

The auto-archive policy moves completed issues into the team’s archive after a selected period. Available periods range from one week to one year.

The policy applies to issues completed in a Done group status. See Archive and delete issues for the effects of archiving.