Skip to main content

Issues overview

An issue is a single quality defect or task on your project — a crack, a missing fixture, a snag to fix. Issues are the heart of Builddar. Your team logs them, assigns them, tracks them through a workflow, and resolves them.

What an issue holds​

Every issue has:

  • A title describing the problem, and an auto-assigned issue number.
  • A location — the zone it's in, and optionally a pin on a drawing.
  • A status from your project's workflow (for example Open → In Progress → Completed → Validated).
  • An assignee — a company responsible, and optionally a specific person.
  • A priority (high or normal) and a due date.
  • Comments, photos and files, and a full activity history.
  • Optional watchers who get notified of changes.

The issue lifecycle​

  1. Create an issue when you spot a defect — give it a title, a location, and a due date.
  2. Assign it to the responsible company (and person).
  3. Work happens; the assignee moves it through the workflow and adds comments and photos.
  4. It's validated (or rejected) as work is checked.

The exact statuses and who can move between them are defined by your project's workflow.

Who can do what​

  • Manager and Collaborator — can create issues, edit any issue, change status, assign, comment, attach photos, and use bulk actions.
  • Guest — company-scoped. Sees only their own company's issues (plus any assigned directly to them). Can change status (within the transitions their role allows), comment, and attach photos, but cannot create, edit, or delete issues.
note

Because guests are company-scoped, an issue that isn't assigned to a guest's company simply won't appear for them.

Guides in this section​

See also Pin issues on a drawing.

Last updated on