Custom Fields

Create reusable fields to capture consistent metadata across work.

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.

1

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

2

Add the field

Click Add custom field.

3

Configure the field

Common configuration:

• Name (for example: Workstream, Client, Phase)
• Type (text, number, date, dropdown, multi-select, checkbox, URL)
• Default (optional)
• Required (optional)

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
• Filtering and Sorting Data
• Project Settings and Configuration
• Exporting Data from Views