The big picture
A place to run delivery work — milestones, tasks, issues, time and discussion, per project.
Projects is a lightweight work-management space for anything you deliver over time — an installation, a custom build, an implementation. Each project bundles milestones, tasks, an issue tracker, time logs, documents and a discussion board, with a customizable dashboard on top.
Where the screens live
- Projects list —
/projects(grouped, filterable by status). - Project detail —
/projects/<id>— a nine-tab cockpit (§06). Create/edit and My-Timesheet open as pushed screens.
Projects is a Growth / Business plan feature (not on Lite). Permissions: canViewProjects to see, canManageProjects to manage — plus a per-project manager override: the project's manager can manage it even without the global flag. Non-elevated staff see only their own and shared projects.
The project
Owner, team, dates, visibility — and where it came from.
A project manager sets the status from the pill in the project header — any status can be picked at any time; it's a label, not a gate. The one nudge: when every milestone is Completed or Skipped on an Active project, Deetzo offers Mark project Completed.
- Team — a manager plus members; an access index scopes who can see a private project. Visibility is
privateorshared. - Groups — organise projects into folders (e.g. "Manufacturing").
- Origin — a project can link to the CRM lead it came from (there's no separate customer field; the lead is the only "client" link).
- Progress — the header bar is Completed tasks ÷ tasks that aren't Cancelled (falling back to Completed ÷ all milestones when there are no tasks).
- Extras — custom fields, web links (external tabs), a Status workflow (greys out disallowed moves in a project task's status menu), and save-as-template.
Milestones
The project's phases.
Deetzo's "phases" are milestones — ordered checkpoints embedded in the project. New projects seed a default set (Design → Planning → Production → Quality → Dispatch), which you edit freely.
- Each milestone has an owner, a deadline, an order, and an internal / external (customer-facing) flag.
- When every task under a milestone is Completed or Cancelled (at least one Completed), the milestone auto-advances to Completed and the next Pending milestone moves to In Progress. It happens on Deetzo's servers the moment the last task is finished — from My Tasks, the task itself or the phone — without anyone opening the project.
- Milestones are ordered, not dependency-linked — reorder them, but there's no critical-path between milestones.
Tasks
The same tasks as everywhere else — attached to a project and milestone.
Project tasks are the same task objects used across Deetzo (see the Tasks & Collaboration guide), linked here by a project and milestone. Three views:
Tasks carry a full toolkit — assignee, checklist, participants, sub-tasks, a finish-to-start predecessor (advisory), estimate hours, and custom fields. Per-user saved views persist your grouping and columns.
Issues
A built-in bug / issue tracker, per project.
Each project has an issue tracker (IS-0001) for defects and blockers, separate from tasks.
| Field | Values |
|---|---|
| Severity | low · medium · high · critical |
| Status | open · in_progress · in_review · closed · reopened (only closed counts as closed) |
| Also | assignee, reporter, due date, component label, linked tasks, resolution note, attachments |
Per-severity SLA hours and display labels are configurable (Issue-tracker settings), and overdue-vs-SLA issues escalate.
Time logs
Hours against the project — and an honest note about what they are.
Team members log hours against a project (optionally a specific task), grouped by week with per-member subtotals. The total surfaces as a header KPI, and My Timesheet gives you a cross-project view of your own logs.
Project time logs record hours with no rate, no billable flag, no approval, and no cost. They don't roll into budget or invoicing (there is none — see §07). If you need approvals or billable time, that's the separate HR Timesheet module (/timesheet · /approvals), which is unrelated to project profitability.
The project cockpit
Nine tabs, and a dashboard you build yourself.
- Dashboard — drag-and-drop widgets (task status, milestones, overdue, team, time logs, issue status, progression); layouts save per user, and can embed saved reports.
- Reports — a library (created-vs-completed, milestone completion, …) plus a custom report builder.
- Documents — Drive uploads, aggregated with attachments from the project's tasks.
- Discussions — threaded forums per project (pin, reply).
- Users — manage the manager and members.
- Automation — server-side rules (on task-created / status-changed / field-updated / due-date-reached) to auto-act.
What's not here
So you don't go looking for it.
- No budget, cost, billing type, hourly rate, profitability, or invoicing from a project. Projects track work (tasks, milestones, issues, hours) — not money. There's no link from a project to a Sales invoice.
- "Phases" are milestones — there's no separate phase entity, and milestones have no critical-path dependency.
- Two time-tracking systems exist and shouldn't be conflated: project time logs (hours, here) and the HR Timesheet module (weekly grid + approvals, elsewhere).
Quick reference
The essentials.
| Concept | Values |
|---|---|
| Routes | /projects · /projects/<id> |
| Project status | active · on_hold · completed · cancelled |
| Milestone status | pending · in_progress · completed · skipped |
| Issue severity | low · medium · high · critical |
| Issue status | open · in_progress · in_review · closed · reopened |
| Detail tabs | Dashboard · Tasks · Reports · Documents · Milestones · Time Logs · Issues · Discussions · Users |
| Permissions | canViewProjects · canManageProjects (+ per-project manager) |
| Plan | Growth / Business (not Lite) |
A project is a container for work, not money. Milestones are the phases, tasks and issues are the work, time logs are the effort — all in one cockpit with a dashboard you shape. Just don't expect budgets or billing here.