#Collaboration Best Practices
Strong collaboration in Hawzu comes from clear ownership, shared vocabulary, disciplined access, and traceable work.
#Write for the Next Person
- Use clear titles and descriptions.
- Explain why a test or defect matters.
- Add execution notes when a result needs context.
- Keep comments and defect updates factual and actionable.
Clear work reduces back-and-forth between QA, product, and engineering teams.
#Use Shared Assets Carefully
- Use shared steps for repeated flows.
- Use parameters for reusable non-secret values.
- Use custom fields only when they improve filtering, reporting, or required capture.
- Use labels consistently across test cases, requirements, releases, and defects.
Shared assets should reduce duplication without creating hidden complexity.
#Manage Access Through Groups
- Create groups for teams or responsibilities.
- Assign groups to projects with the right project role.
- Use direct project roles only when individual access is intentional.
- Review inherited access before removing a user from a project.
Learn more in Groups Overview and Managing Users.
#Keep Defect Collaboration Structured
- Link defects from failed test cases when possible.
- Review similar defects before creating duplicates.
- Use comments and notifications for triage.
- Link external issues when engineering work is tracked outside Hawzu.
Learn more in Defects and External Issues.
#Use Integrations as Bridges
Use integrations to connect workflows, not to replace Hawzu as the testing record.
- Use Slack for selected defect notifications.
- Use Jira, GitHub Issues, GitLab Issues, Azure DevOps, or Linear for external issue handoff.
- Keep project scope tight.
- Avoid assuming every field mirrors automatically between tools.
#Next Steps