Skip to content

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.


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

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


Use Text Box for short text values.

Examples:

  • Browser version
  • Build number
  • Customer code

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.


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.


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.


Use Date Picker for calendar dates.

Date defaults are selected from the date picker.


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.


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.


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.