Skip to content

Projects and tasks

The Project app (Pro+ tier) tracks the work your team does — for internal initiatives or for customer-billable projects.

Anatomy

A project is a container. Inside, tasks are the units of work:

Project: Acme Website Build
├── Task: Design home page
├── Task: Build CMS
├── Task: Configure hosting
├── Task: User testing
└── Task: Launch

Each project has:

FieldWhat
NameThe customer-facing project name
CustomerThe buyer; for invoicing
ManagerThe PLANA user responsible
MembersWho works on it
StagesCustom kanban columns (e.g. Backlog / In Progress / Review / Done)
Analytic accountFor per-project profitability
Billing typeNone / Hourly / Fixed / Milestones

Tasks

Each task carries:

FieldWhat
Title / descriptionWhat to do
Assigned toWho is on it
StageCurrent status in the kanban
DeadlineWhen it needs to be done
TagsOptional categorisation
SubtasksBreak into smaller steps
Dependencies"Wait for task X before starting"
TimesheetsHours logged against this task

Views

ViewWhen
KanbanDefault — visual swim lanes by stage
ListTabular with sortable columns
GanttTime-based, dependencies visible
CalendarDeadline-focused
MapIf tasks have locations (field service)

Status workflow

The default stages: In Progress → Done → Cancelled. Customise per project.

For an agile workflow, common stages:

  • Backlog — not yet started
  • Next — committed for the current sprint
  • In Progress — actively worked on
  • Review — done, awaiting QA / approval
  • Done — accepted
  • Cancelled — abandoned, with a reason

Move tasks between stages by dragging in the kanban view.

Tasks linked to sale orders

When a sale order is for service work, PLANA can auto-create the project and tasks from the order:

  • Sale order with a "service" product → on confirm, generates a project
  • Project's customer = sale order customer
  • Sale order's quantity = task budget hours (for hourly billing)

Where to read more

© PLANA Digital Ltd.