Jump to
↵select↑↓navigateescclose

ERPNext TaskView

A project and task workspace for ERPNext, with timers and hour budgets for staff and a portal where customers follow and work on their projects.

Updated
On this page

ERPNext's stock project and task screens are built for record keeping. ERPNext TaskView turns them into a workspace for running a day of work. Your team sees every project as a tree of tasks, starts a timer with one click and watches hours against budget while they work. Your customers get a portal at /projects where they follow progress, add tasks, comment and attach files.

It is for service teams that bill by the hour and want clients to see the same picture they do. It runs on Frappe v16 and is free software under the MIT licence.

What you get

A project and task tree for staff

Task View is the default list view for both Task and Project. Each project is a tree of tasks and subtasks that you can drag to reorder or re-parent, edit in place, and fill with quick entry. All Tasks, My Tasks and Pinned switch between everything, your assignments and your personal shortlist, and a side panel opens the full form without leaving the tree. See Work the task tree.

Timers that log to Timesheets

Start, pause and stop a timer on any task. The time goes to a draft Timesheet as you work, and a floating dock on every desk page shows what is running. See Timers and timesheets.

Hour budgets

Tasks and projects with a budget show a meter such as 12.5 / 20 h that turns amber at 80% and red when over. Budgets roll up from subtasks, and logged hours are live: draft timesheets and running timers count. See Hour budgets.

A client portal

Customers sign in to /projects and see only their own projects: an overview with a budget per phase, tasks as a list or a kanban board, time logs, comments and files. When a customer acts, the team is notified. See The client portal.

Where to start

You areRead
Staff working in the deskWork the task tree, then Timers and timesheets and Hour budgets
A client with a portal loginUsing the client portal
The administrator setting it upInstall and upgrade, Configuration and Giving customers access
A developer changing the appDevelopment and How it works

Requirements

  • A bench with Frappe v16. The app declares frappe >=16.0.0,<17.0.0.

  • ERPNext on the same site. The app extends ERPNext's Task, Timesheet and Timesheet Detail classes, so install ERPNext first and TaskView after it.

  • Node and yarn on the machine that builds the app. bench build runs the app's yarn build.

These pages describe the code in the repository. Where a statement depends on Frappe's or ERPNext's own behaviour, the page says so and names the version it was checked against (Frappe 16.34 and ERPNext 16.35).

Source and changes

The source is at github.com/Avunu/erpnext_taskview. History is in the changelog.