Custom Fields

Custom Fields extends standard records with tenant-specific data, defined under Settings Work Item Types on the Fields tab alongside Types and Defaults. Fields are reusable definitions with a per-type assignment: define once, then pick which item types each one appears on. Reference fields are created and assigned from each type’s Relationships tab.

The rows shown are Child Project (relationship_campai…, Reference), Child Project (relationship_copy_do…, Reference), Completed (completed, Date and Time, on Task, Program, and one more type), and Copy Document (relationship_deliver…, Reference, on Task). The table columns are display name, system name, type, description, and item types, with search, sort, columns, and advanced filters above and 1 to 25 of 44 results in the pager.

• One field holds one fact. A field that holds two facts cannot be filtered, defaulted, or trusted in a view.
• Name fields for the fact, with the naming guide beside you. Renames later are possible but noisy, since records already written keep history.
• Check Objects and Work Item Types before adding: the fact may already have a home, and duplicates split the record across two fields.
• Retire fields that stopped meaning anything. A dead field that stays visible invites entries that go nowhere. Add field creates one.

What next

• Objects: the object groups these fields extend.
• Work Item Types: the work-side types and defaults.
• Table Views: the saved views that surface these fields.