# Custom fields & tags

Fields and tags add your own information to tickets — fields structured and per project, tags
free and across the whole account.

## Ticket fields

Ticket fields such as status, priority, or customer type appear on every ticket in a project
and can be used for filtering and sorting. They come as select, multi-select, checkbox, text,
and date.

1. In the ticket list, open **Manage ticket fields**.
2. Click **New field**, pick the field type, and give it a label.
3. For select fields you add options with a color; date fields can be marked as a
   **due date**.

A field's internal name can no longer be changed once tickets use it. Ticket fields are
managed by whoever administers the project.

## Linking options to system functions

For select and multi-select fields, each option has an **Options** area with checkboxes like
**New**, **Completed**, or **High Priority**. This isn't a duplicate of your label: an option's
name (e.g. "new") is plain text that only humans read. Only the checkbox tells Lalabase what
the option *means* — name an option "new" but leave the **New** checkbox unchecked, and it
stays an ordinary option with no special meaning to the app.

Two groups have a real effect:

- **Status** (Backlog, New, Open, In Progress, Completed, Closed) only affects your project's
  status field. An option marked **Completed** or **Closed** counts as done — that decides, for
  example, whether a ticket can be overdue, how sub-task progress is calculated, and whether a
  column sorts to the end of the Kanban board.
- **Priority** (High Priority) can be set on any select option in any field, not just a
  dedicated priority field. Tickets with such an option get a red highlight in ticket lists and
  on some dashboard widgets.

Multiple options can share the same function — for example if both "Accepted" and "Done"
should count as **Completed**.

## Tags

Tags are free keywords. Unlike fields, they apply account-wide and connect tickets, notes, and
documents. You assign them right when creating or editing a ticket via the tag field.

<div class="docs-callout docs-callout--info">
  <div class="docs-callout__title">Field or tag?</div>
  <p>Use a <strong>field</strong> for structured, filterable values within a project (status, priority). Use a <strong>tag</strong> for loose, cross-project grouping.</p>
</div>