Project custom fields appear in the views selected during project field configuration.
The current supported views are:
Fields assigned to Testcase appear when creating or editing repository test cases.
They can also participate in repository filtering when the field supports structured filtering, such as dropdown fields.
Fields assigned to Requirement appear when creating or editing requirements.
Required requirement fields must be completed before the requirement can be saved.
Fields assigned to Release appear when creating or editing releases.
Release custom fields help capture project-specific release information such as risk, environment, or rollout details.
Fields assigned to Defect appear when creating or editing defects.
Defect custom fields can support triage, ownership, severity workflows, customer impact, or integration-specific metadata.
If a field is required in a selected view, users must provide a value before saving that item.
Hawzu lists missing required custom fields so users know what to complete.
Default values can pre-fill new items in the selected views.
For dropdown fields, the default is the option marked as default. For other field types, the default comes from the configured value.
When a required field with a default is added to views that already have data, Hawzu may show an impact summary and apply the default to existing items.
Disabled or deprecated fields are not intended for new data entry.
Existing values can remain visible for reference, especially in details views where historical information matters.