Manage project custom fields

You will learn how to create, edit, archive, reorder, and use custom fields in a project.

For the concept model and field types, read Custom fields.

Open custom field settings

Open the project, then go to Project settings and choose Custom fields.

Only project admins can manage field definitions. Project members who can edit issues can set custom field values on issues they can update.

Create a field

Choose New custom field.

Fill in:

Name: use a short label people will recognize in issue detail, filters, and table columns.
Type: choose Short text, Number, Date, Single select, or User.
Issue types: choose the issue types where the field applies, or leave the field available to all issue types.
Minimum / maximum: add numeric limits when the number field has a real range.
Options: add the allowed choices for single-select fields.

Save the field. It becomes available on matching issues and in table column and filter controls.

Choose the right type

Pick the narrowest type that matches how the team will use the value:

Use Short text for compact names or IDs that do not need paragraphs.
Use Number when people will compare or filter numeric values.
Use Date for a date-only commitment, target, or review point.
Use Single select when the value must come from a controlled list.
Use User when the answer should be a workspace member.

If people keep entering the same short text values, consider changing the process to a single-select field so filtering stays consistent.

Edit a field

Open a field from the Custom fields settings page.

You can update the field name, config settings (such as number min/max), issue-type scope, and single-select options. For single-select fields, keep option labels stable when they already appear on many issues.

Changing issue-type scope controls where the field appears going forward. It does not automatically rewrite older issue history.

Reorder fields

Use the reorder controls on the Custom fields settings page to choose the order people see fields in issue surfaces and project metadata controls.

Put the fields people fill most often near the top. Keep rare reporting fields lower so triage stays fast.

Archive or restore a field

Archive a field when the team no longer actively uses it but may need the historical values later.

An archived field is hidden from normal issue editing and active field pickers. Stored values are preserved. Restore the field when the team needs to use it again.

Delete a field

Delete only fields that were created by mistake or whose data can be safely removed.

Deleting a field removes its definition, options, and stored issue values. If you are unsure, archive the field instead.

Set values on an issue

Open an issue and edit the custom fields section. Tixio shows fields that apply to the issue's type.

Set the value that matches the field type:

Short text: type a compact text value.
Number: enter a numeric value.
Date: choose a date.
Single select: choose one option.
User: choose one workspace user.

Clear a value when it no longer applies. Clearing the value affects only that issue.

Use columns and filters

Open project Issues and switch to table view.

Use column controls to show or hide custom fields. This is useful when reviewing many issues with the same project-specific data, such as severity, customer tier, review date, or support owner.

Use the filter bar to narrow issues by custom field value. You can filter by option, user, text, number, date, and empty or not-empty states depending on the field type.

For broader view behavior, read Use issue views and backlog. For filter query details, read Filter query language.