Project & Task Tracking Software

The rules it enforces

Not aspirations — guarantees. Each of these is a documented behaviour of the module, covered by a test.

Work is never given to someone who has left.

Neither a project owner nor a task assignee may be a terminated employee — checked at creation and on every reassignment, against the same directory HR uses.

A project cannot be completed while work is still open.

Finish or cancel the outstanding tasks first. That is the invariant that makes a completed project a fact rather than a mood.

Completion is reversible; cancellation is final.

Work is routinely found to be incomplete, so reopening is allowed and clears the completion stamp. A cancelled project, though, takes no new work.

Work only goes to people who are on the project.

A member is someone the project can give work to — that is the whole definition, and the assignee picker honours it.

Project codes are unique per organisation.

Compared case-insensitively, so “ACME-2” and “acme-2” can never be two different projects.

What it lets people do

• Start a new project.
• See projects and their progress.
• See every project in the organization, not only the ones you are on. Reading only — never update, create or assign.
• Change a project's details, including completing or cancelling it.
• Add a piece of work to a project.
• See the work on a project.
• Change a task's title, notes, priority, due date, estimate or status.
• Give a task to someone, or take it off them. Deliberately separate from update: editing work and reassigning a colleague's work are different authorities (ADR-0016).
• Put people on a project, and take them off it. Separate from editing the project itself: deciding who is on a team is its own authority.

Runs inside