Skip to content

Project & Events

1. Purpose

Project organises work into projects and tasks, with stages, assignees and deadlines. Events manages internal or public events with registrations.

Neither is a headline NestERP feature. Both are present because other modules require them: thalia_invoice_reminders uses Project to structure follow-up work, direct_budget_management budgets against projects, and hrms_dashboard requires Events.

2. Features

Project

  • Projects containing tasks, each with a stage, assignee and deadline
  • Kanban and list views of the task pipeline, with configurable stages
  • Subtasks and task dependencies
  • Time logged against tasks through Timesheets
  • Milestones and deadlines
  • Customer-visible tasks through the portal
  • Project-level reporting on progress and time spent

Events

  • Events with dates, venue and capacity
  • Attendee registration and confirmation
  • Event categories and templates
  • Attendance tracking

3. Where to find it

  • Menu: Project → Projects / Tasks; Events → Events / Registrations
  • Technical names: project, event
  • Tier: Odoo core (Community Edition)
  • Available in: project on Odoo 17; event on Odoo 17 and 18

4. Modules used

Module Tier Why it is needed
project Odoo core Projects, tasks, stages
event Odoo core Events and registrations
hr_timesheet Odoo core Logging time against project tasks
analytic Odoo core Project cost tracking through analytic accounts

NestERP and third-party modules that require these

Module Requires Why
thalia_invoice_reminders project Structures the overdue-invoice follow-up work
direct_budget_management project Budgets defined and compared per project
hrms_dashboard (Cybrosys) event HR dashboard includes event data

5. Configuration

  1. Create projects — Project → Projects → New. Set the project manager and whether tasks are visible to customers.
  2. Configure task stages per project, matching the client's actual workflow rather than the defaults.
  3. Enable Timesheets on the project if time is to be logged against its tasks.
  4. Set the analytic account on the project if costs should be tracked against it.
  5. For events — create event categories and templates, then the events themselves with dates and capacity.

Configuration traps

  • Task stages are per project by default, so every new project starts from the default set. Agree a standard stage list and apply it consistently, or reporting across projects becomes meaningless.
  • Customer-visible projects expose task names and descriptions through the portal. Check what is written in them before enabling.
  • Project analytic accounts must exist before cost tracking works; the link is not created automatically.

6. How it's used

  1. Project Manager — creates the project and its stages.
  2. Project Manager — creates tasks, assigns them and sets deadlines.
  3. Assignee — moves tasks through stages and logs time on their timesheet.
  4. Project Manager — reviews progress and time against budget.

For events:

  1. Organiser — creates the event with dates and capacity.
  2. Organiser or attendee — registers attendees.
  3. Organiser — confirms registrations and tracks attendance.

Screenshots needed

Save to docs/assets/project-events/: project kanban · a task form · project list with progress · an event with its registrations.

7. Access rights

Group Can do
Project / User Work on tasks assigned to them
Project / Administrator Create and configure projects and stages
Events / User Manage registrations
Events / Administrator Create and configure events
Portal See customer-visible project tasks only

8. Version differences (16 / 17 / 18)

  • Neither module is part of our Odoo 16 line.
  • attrs and states removed from views.
  • project required by thalia_invoice_reminders and direct_budget_management; event required by hrms_dashboard.
  • <tree> elements superseded by <list>.
  • event still required by hrms_dashboard. project is not required by any Odoo 18 module in our stack — the Thalia finance modules that need it are 17-only.

9. Known limitations

  • No Gantt or resource-planning view. Enterprise.
  • No project profitability report out of the box on Community; cost tracking is through analytic accounts and manual reporting.
  • No project billing / invoicing from timesheets in the NestERP configuration.
  • No field service or helpdesk. Both Enterprise.
  • Events has no website registration without the Website module, which is outside the NestERP stack — registration is internal only.
  • Both are dependency-driven, not requested features. Present at clients who never open them.

Needs verification on the Thalia live instance

  • Whether Project is actively used, or present only as a dependency
  • Which projects exist, and whether thalia_invoice_reminders created any of them
  • Whether tasks are customer-visible through the portal
  • Whether Events is used at all
  • Whether project analytic accounts are set and reported on