Ownership
Use ownership to show who is responsible for moving work forward and who needs visibility.
Ownership fields
Initiatives, bugs, issues, pull requests, and todos can include several people fields:
| Field | Meaning |
|---|---|
| Owner | The person accountable for moving the work forward. |
| Assignees | People doing or contributing to the work. |
| Reviewer | The person who needs to review the work. |
| Reporter | The person who reported the bug, issue, or request. |
| Teams | The teams responsible for the work or needing visibility. |
Use ownership to plan
Plans are stronger when every active item has an accountable person. Use ownership fields when grouping boards, finding unassigned work, running triage, preparing standup, and reviewing blockers.
The assignee filter on initiatives includes Unassigned, which helps isolate roadmap work that has not been assigned to anyone yet.
When work moves between people, update the owner or assignees instead of leaving the change buried in comments. Status tells the team where the work is; ownership tells them who can move it.
For formal access boundaries, see Permissions.