Example: Project Management

The Project Management preset rolls out two related entities: Projects and Tasks.

Entities and relations

Projects (projects) ──1:∞── Tasks (project_tasks)

Each task is required to be linked to a project through the Project field (a one-to-many relation, see Relations Between Entities).

Project status

Planning → Active → Completed
                  ↕
              On Hold
                  ↓
              Canceled

Status	Allowed transitions
Planning	→ Active, Canceled
Active	→ On Hold, Completed, Canceled
On Hold	→ Active, Canceled
Completed	— (final)
Canceled	— (final)

The project also has Project manager, Start date, Deadline, Budget, and Priority (Low / Medium / High) fields.

Task status

The task uses a separate state model — effectively a kanban board:

Backlog → To Do → In Progress → In Review → Done
                            ↓           ↓
                        Canceled   In Progress (sent back for rework)

Status	Allowed transitions
Backlog	→ To Do
To Do	→ In Progress, Canceled
In Progress	→ In Review, Backlog, Canceled
In Review	→ Done, In Progress
Done	— (final)
Canceled	— (final)

Additional task fields: Priority (Low/Medium/High/Blocker), Assignee, Reporter, Due date, Estimate (hours).

Automations

Rule	Trigger	What it does
Set reporter on creation	Before Create	If the "Reporter" field is empty, fills it in with the current user
Notify assignee when assigned	After Update	When the "Assignee" field changes, sends them a push notification
Notify reporter on completion	After Update	When the status moves to "Done", notifies the reporter
Notify assignee of sendback from review	After Update	When the status moves from "In Review" to "In Progress", notifies the assignee that rework is needed

The project has a similar rule, "Notify owner of status change".

"Task Execution" business process

When a task is created, a BPMN process with a review cycle starts automatically:

Task created
   ↓ automatically
Status → "In Progress" + assignee notified
   ↓
Process task: "Complete task" (for the assignee)
   ↓ on completion
Status → "In Review" + reporter notified
   ↓
Process task: "Review result" (for the reporter)
   ↓ on completion
  [Accepted?]
   ↙          ↘
Yes            No
   ↓              ↓
Status:       Status: "In Progress"
"Done"        (rework, assignee notified)

This is the same scenario covered in general terms in the Business Processes and Tasks section (the "Projects: Task execution with a review cycle" example).

Dashboard

By default, the Developer and Project Manager roles see the "Project Management" dashboard: tasks by status, by priority, active projects. See Dashboards and Charts.

Roles

Role	Permissions
Developer	View projects; create/view/edit tasks
Project Manager	Full access to projects and tasks, including delete