Custom fields

You will learn what custom fields are, which field types Tixio supports, and how custom fields fit into issue views, filters, and project administration.

Custom fields let a project capture structured information that is specific to that team's workflow. Use them when built-in fields such as type, priority, assignee, labels, dates, estimates, epics, milestones, and versions are not specific enough.

For setup steps, read Manage project custom fields.

When to use custom fields

Use a custom field when the value should be:

Consistent across many issues.
Filterable or visible as a table column.
Limited to a known type, such as a number, date, option, or user.
Managed by project admins instead of typed differently on each issue.

Use labels for looser categories such as frontend, blocked, or customer-request. Use a custom field when the data has a stable meaning, such as customer tier, support plan, severity score, target review date, or owning team member.

Field types

Tixio supports these custom field types:

Type	Use it for	Example value
Short text	Small free-text values.	`Enterprise`
Number	Numeric values that can be compared or ranged.	`4.5`
Date	Calendar dates without a time of day.	`2026-07-02`
Single select	One value from a project-managed option list.	`High`
User	One workspace user.	A support owner

Short text values should stay compact. If the value needs paragraphs, links, or discussion, put that information in the issue description or comments instead.

Definition settings

Each custom field definition belongs to one project. Project admins can choose:

Name: the label people see on issues, filters, and table columns.
Type: the value shape. A field's type cannot be used interchangeably with another type.
Issue types: optional scope such as Bug, Task, Story, or Epic. Empty scope means the field can appear on any issue type.
Minimum and maximum: optional constraints for number fields.
Options: the allowed values for single-select fields.

Values on issues

Custom field values live on the issue. Different field types store different value shapes:

Short text stores text.
Number stores a numeric value.
Date stores a YYYY-MM-DD date.
Single select stores one option.
User stores one workspace user.

Clearing a custom field removes the issue's value for that field. It does not delete the field definition or affect values on other issues.

Table columns and filters

Project table view can show custom fields as columns. Use custom field columns when you need to compare many issues without opening each detail page.

The filter bar can filter by custom field value. Depending on the field type, you can filter for exact options or users, text matches, number/date values, or empty and not-empty states.

For query syntax, read Filter query language.

Archive and delete behavior

Archiving a custom field hides it from issue-entry surfaces while preserving the definition and stored issue values. Use archive when a field is no longer active but historical data may still matter.

Deleting a custom field permanently removes the definition, options, and stored values. Use delete only when the field was created by mistake or the data is no longer needed.