Auri PMS (Project Management System) - Plan. Track. Deliver. Projects, tasks, milestones, timesheets, estimates vs actuals and management dashboards for ERPNext v16
# Auri PMS
**Project Management System**
[](https://github.com/anoopverma-collab/Auri_PMS/actions/workflows/ci.yml)
A centralized platform for project planning, task management, timelines, effort tracking, team collaboration and delivery monitoring, built for **ERPNext v16**. Suitable for projects, tasks, milestones, timesheets, estimates versus actuals and management dashboards. Log, assign, track and close work items (bugs, features, tasks, support requests) against ERPNext Projects, plan them into sprints and releases, log time against them and report progress to clients. One screen to create an item, one list to work from, and no configuration beyond adding project members.
* Frappe v16 + ERPNext v16 (required app), standard Desk UI only, Frappe Cloud compatible
(no OS packages, no custom bench commands at runtime).
* Module: **Auri PMS**. Nothing in Frappe or ERPNext core is modified: everything is added through
hooks, Custom Fields, Custom DocPerms and `doc_events`.
## Features
| Area | What you get |
|---|---|
| Tickets (Work Items) | bugs, features, tasks and support requests with parent/child tickets, priorities, categories, start/due dates, estimates, relations and blockers; per-project ticket numbers such as `AURI-00001` |
| Ticket Types and workflow | configurable ticket types with default status, *Counts as Defect* flag and allowed status transitions per project role |
| Project Hub | project-first screen: users only see projects they belong to (or public ones) and work inside the chosen project |
| Roles and access | project roles with nine capability flags; private projects stay hidden from outsiders |
| Sprints | start/end dates, goal, add tickets to a sprint, Start / Complete, Sprint Board and Burndown |
| Releases | group tickets into versions with progress and due date |
| Modules | tag every ticket with the module (part of the product) it is for, such as Sales, Stock or Accounts; dashboards, reports and the client report break the numbers down by module |
| Risk Register | one record per project risk with probability x impact scoring (Low, Medium, High, Critical), owner, mitigation plan and due date; open risks feed the project health status, the dashboards and the client report |
| Kanban board | one column per status, drag a ticket to change its status (blocked moves are refused) |
| Gantt chart | tickets drawn from start date to due date, filtered to the project |
| Time tracking | log hours per ticket with activity type and a *Billable* flag; limits per entry/day and lock days |
| Dependent on Client | tick a ticket that waits on the client; tracked with a note and *Waiting since* and counted everywhere |
| Dashboards | Project Health (with a risk heat map and tickets by module), Portfolio (risks per project), My Work (risks I own), Quality (bugs by module) and Client Status Report (progress by module, risks and mitigation) |
| Themes and range | 8 themes in light and dark and a 1 month / 3 months / 6 months / Overall range, shared by all dashboards |
| Reports | Work Item Summary, Time Log Summary, Release Progress, Overdue Work Items, Sprint Summary, Sprint Burndown, Client Dependencies |
| Email | email a project's status report (preview, PDF, weekly schedule), daily due-date digests, optional email-to-ticket intake |
## Screenshots
All screenshots use the sample Auriga project data. Every screen is shown in **light** and **dark** mode: the app follows Frappe's own light/dark setting (user menu, *Toggle Theme*), so nothing needs configuring.
### Project Hub
The starting point. It lists only the projects you belong to (plus public ones); each card shows open, overdue, your own tickets, team size and the active sprint. Open a project to work inside it.
 |  |
| Light mode | Dark mode |
### Project overview
One project's workbench, laid out in aligned rows: the sprint with its burndown next to open tickets by status and type; tickets waiting on the client and open tickets by module next to the risk register; sprints, releases and team side by side; and the 10 most recently changed tickets. The *Views* and *Reports* menus open the list, Kanban, Gantt, risk register and reports already filtered to this project.
 |  |
| Light mode | Dark mode |
### Project Health
The client-facing health view. The banner gives the status (On Track, At Risk or Off Track), a score and every reason behind it, including open risks and overdue mitigations. Below it: complete %, open and closed tickets, overdue, waiting on the client, hours, then paired panels for created vs resolved, backlog trend, tickets by type, module, status and priority, waiting on the client, estimated vs spent hours, a full-width **risk register** (probability x impact heat map and the top open risks), time and activity, people, sprint velocity, ageing and releases. Use the *Range* menu for 1 month, 3 months, 6 months or overall.
 |  |
| Light mode | Dark mode |
### Portfolio
Every project you can see on one screen, for management. The banner summarises the health of the projects that have the Portfolio switch ticked, and the table compares open tickets, overdue %, done %, budget burn, billable % and client-waiting tickets. Click a project to open its health view.
 |  |
| Light mode | Dark mode |
### My Work
A personal page for the signed-in user: open tickets grouped by due date (overdue, today, this week, later), what is blocked or waiting on the client, hours logged this week against the weekly capacity, active sprints, and one-click *Log time*.
 |  |
| Light mode | Dark mode |
### Quality dashboard
Bug quality across projects: bugs opened vs fixed, critical open bugs, time to fix by priority, reopen rate, bugs per 100 hours, bugs by category and project, and the age of open bugs. A ticket type counts as a bug when *Counts as Defect* is ticked.
 |  |
| Light mode | Dark mode |
### Client Status Report
A client-ready report for any period, previewed exactly as it will be emailed or exported to PDF: status, delivered tickets, what is in progress, what is waiting on the client, hours, plan and risks. Email it, download the PDF, or let it go out weekly. Every send is logged.
 |  |
| Light mode | Dark mode |
### Client Dependencies report
The drill-down behind every *Waiting on client* number: each open ticket that depends on the client, how long it has waited and what is needed. Tick *Dependent on Client* on a ticket to put it here.
 |  |
| Light mode | Dark mode |
### Kanban board
One column per ticket status. Drag a card to change its status; a move the workflow does not allow is refused.
 |  |
| Light mode | Dark mode |
### Gantt chart
Each ticket drawn from its start date to its due date, so overlaps and slips are visible. Zoom with the Quarter Day, Day, Week, Month and Year buttons.
 |  |
| Light mode | Dark mode |
### Risk Register
One record per project risk. Probability and impact are each scored 1 to 5, the score is their product, and the level follows from it (Low 1-4, Medium 5-9, High 10-14, Critical 15-25). Each risk has an owner, a status (Identified, Mitigating, Monitoring, Occurred, Closed), a mitigation plan and due date, a contingency plan and an optional related ticket. Open risks lower the project health status and appear on the project overview, Project Health, Portfolio and My Work; risks ticked *Show in Client Status Report* are listed with their mitigation in the client report.
 |  |
| Light mode | Dark mode |
 |  |
| Light mode | Dark mode |
## App themes
The dashboards (Project Hub, Project Health, Portfolio, My Work, Quality and Client Status Report) share one theme. Pick it from the **Theme** menu at the top right of any dashboard; the choice applies to all of them and is remembered in your browser. The 1 month / 3 months / 6 months / Overall **Range** menu is shared the same way.
Every theme has a light and a dark version. The version follows Frappe's own light/dark setting, so a user who switches Frappe to dark mode gets the da