Custom fields

Each project owns its own set of custom fields — there is no global registry. The schema lives in Project Settings → Custom Fields.

Field types

• Text — single-line free text.
• Single-select — one value from a fixed list of options (configured in the field's settings).
• Multi-select — zero or more values from a fixed list.
• Date — calendar picker.
• User — a project member.
• Link — URL with optional label.

Creating fields

In the Custom Fields tab:

• Click + New field to define one from scratch (name + type + options).
• Click + From library to pick from a curated catalog (recommended). Includes single fields and pre-built bundles like "QA basics", "Bug tracking", "Agile", "Mobile".

Editing values

In the test case detail panel, custom fields appear under the standard fields. Each field renders the editor for its type. Changes save automatically on blur.

Why per-project, not global

Different projects have different domains. A "Component" field in a backend project is a list of microservices; in a mobile project it's "iOS / Android / Tablet". Per-project schemas avoid pollution and let teams iterate without coordination.