Custom fields have two levels in Hawzu: workspace definitions and project configuration.
Understanding the difference prevents accidental global changes and helps projects stay flexible.
Workspace fields define the shared field itself.
At the workspace level, users can manage:
Workspace fields can be reused by projects, but they do not automatically appear on project work items.
Project fields decide how a field behaves in one project.
At the project level, users can configure:
Project configuration lets the same field be important in one project and hidden in another.
In a project, fields with Workspace scope come from the workspace field catalog.
Project users can configure how these fields behave locally, but they do not change the workspace definition.
For example, a project may enable Environment for defects only, while another project may enable the same field for test cases and releases.
Fields with Project scope are created for the current project.
They are useful for project-specific needs that should not become part of the shared workspace catalog.
Project-scoped fields can be removed or deprecated within that project according to usage.
Workspace page:
Project page:
Use workspace fields for shared language. Use project fields for local needs.
If multiple projects ask for the same project field, consider creating a workspace field instead.