Skip to content
Hawzu Docs

Field Types and Validation

2 min read

Field type controls how users enter values, how defaults work, and how values appear in work items.

Field type cannot be changed after creation.

Number

Section titled “Number”

Use Number for numeric values that may be compared, sorted, or reported.

When default value is enabled, users must provide a number.

Text Box

Section titled “Text Box”

Use Text Box for short text values.

Examples:

  • Browser version
  • Build number
  • Customer code

Text Area

Section titled “Text Area”

Use Text Area for longer notes or descriptions.

Avoid using Text Area when values need consistent reporting. Use Dropdown instead when values should be controlled.

Checkbox

Section titled “Checkbox”

Use Checkbox for true/false information.

Checkbox defaults are Checked or Unchecked.

Checkbox fields are not shown with the same required-field control during project field creation because the value is always binary.

Section titled “Dropdown”

Use Dropdown for controlled values.

Dropdown fields require at least one active option before the field can be created.

Dropdown options can include:

  • Label
  • Color
  • Icon
  • Default marker

If default value is enabled, one active dropdown option must be marked as the default.

Date Picker

Section titled “Date Picker”

Use Date Picker for calendar dates.

Date defaults are selected from the date picker.

Section titled “Link”

Use Link for URLs.

Link default values must:

  • Start with http:// or https://
  • Include a valid host
  • Use a valid URL format

Invalid link defaults prevent the field from being created or saved.

People

Section titled “People”

Use People to store one or more project users, such as an owner, reviewer, or responsible tester.

A People field can hold a single person or multiple people. This is chosen with the Allow multiple option when the field is created and, like the field type itself, cannot be changed afterward.

  • The picker lists the project’s users and shows each person’s avatar, name, and email. It is searchable and clearable.
  • Single-person fields store one user; multi-person fields store several.
  • Values are stored by the user’s email, so someone who later leaves the project still displays correctly and can be cleared from the field.

When default value is enabled, you choose the default person (or people) from the same picker.

Required And Default Value Rules

Section titled “Required And Default Value Rules”

Required fields need a value before users can save work items in the selected views.

When a field is marked required, Hawzu also enables default-value behavior. This helps existing and new items satisfy the requirement.

For project fields, Hawzu can show an impact summary before applying required/default behavior to existing items.

Why Field Type Is Locked

Section titled “Why Field Type Is Locked”

Changing field type after values exist can make old data invalid.

For example:

  • Text cannot always become a number.
  • A URL may not fit a date picker.
  • A dropdown option may not map cleanly to free text.

Hawzu prevents this by locking field type after creation.

Next Steps

Section titled “Next Steps”