> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/administration/custom-fields.md).

# Custom Fields

### Overview

Custom fields standardize metadata capture across work items.

They support filtering, reporting, and consistent handoffs.

### Key Concepts

* **Custom field**: reusable field added to an item type
* **Field type**: value format, such as text, number, date, or dropdown
* **Scope**: where the field is managed (Account or Project)
* **Option list**: predefined values for dropdown and multi-select fields

### How It’s Used

Use custom fields to capture consistent reporting dimensions.

Use dropdown and multi-select fields for controlled reporting values.

### Benefits

* Cleaner analytics through consistent values
* Faster filtering and triage with repeatable view columns
* Less ambiguity during handoffs and approvals

### Setup Steps

#### Where custom fields apply

Common item types:

* requirements
* tasks
* tests
* Artifacts (when supported)

Custom fields can also be used in views, filters, and exports.

#### Create a custom field

Field scope depends on Account configuration.

{% stepper %}
{% step %}

### Open custom fields settings

Navigate to **Settings** → **Custom Fields** at the required scope.

When scope is unclear, start from Project Settings:

* [Project Settings and Configuration](/organizations-and-projects/project-settings-and-configuration.md)
  {% endstep %}

{% step %}

### Add the field

Click **Add custom field**.
{% endstep %}

{% step %}

### Configure the field

Common configuration:

* **Name** (for example: `Workstream`, `Client`, `Phase`)
* **Type** (text, number, date, dropdown, multi-select, checkbox, URL)
* **Default** (optional)
* **Required** (optional)
  {% endstep %}
  {% endstepper %}

### Best Practices

* Use consistent names across Projects.
* Prefer dropdowns over free-text for reporting fields.
* Keep option lists short and unambiguous.
* Archive fields that are no longer used. Avoid deletion when audit history matters.

### Summary

Custom fields standardize reporting dimensions and improve filterability across work items.

Related:

* [Creating and Customizing List Views](/getting-started/creating-and-customizing-list-views.md)
* [Filtering and Sorting Data](/getting-started/filtering-and-sorting-data.md)
* [Project Settings and Configuration](/organizations-and-projects/project-settings-and-configuration.md)
* [Exporting Data from Views](/getting-started/exporting-data-from-views.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/administration/custom-fields.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.