Tasks — Overview¶
Tasks (internal to-dos and follow-ups) are managed in calServer V2 through the
Notepad module. As in calServer V1 (FrontendNotepad), tasks and maintenance
reminders share one data foundation (the notepad table) and are told apart
by a type:
Type (entry_type) |
Meaning |
|---|---|
task |
Task / follow-up – an assignable to-do with a due date, status and calendar slot. Not linked to a repair. |
maintenance_reminder |
Maintenance reminder – a note linked to a repair (field repair_id/RTAG). See Maintenance overview. |
The type is derived automatically from the repair link: without a repair link the entry is a task, with a repair link it is a maintenance reminder.
Description¶
The tasks module provides centralized task management for the team. Tasks can be created, assigned to a user or a group, given a status and a due date, and tracked in a calendar view. A task can optionally be linked to an inventory item, a customer or a contact.
Feature Set in V2¶
| Feature | Description |
|---|---|
| Task list | Overview of all tasks with filters (status, assignee, type, full text) and sorting by due date |
| Create task | New task with content, due date, status and assignment |
| Status handling | Status transitions via the status system (status type notepad), incl. mandatory-field and follow-up logic |
| Assignment | Assignment to an assignee (assigned_to), a group (assigned_to_group) and additional recipients (additional_recipients) |
| Calendar view | Monthly calendar with drag-and-drop rescheduling and multi-inventory creation |
| Links | Reference to inventory (inventory_id), customer (customer_id), contact (contact_id) and repair (repair_id) |
| Attachments | File attachments per task |
API Endpoints¶
Tasks are managed as a first-class resource via the NotepadController:
GET /api/v2/notepads # List (filter: filter[type]=task)
GET /api/v2/notepads/{id} # Single item
POST /api/v2/notepads # Create
PUT /api/v2/notepads/{id} # Update
DELETE /api/v2/notepads/{id} # Delete
GET /api/v2/notepads/calendar # Calendar view
GET /api/v2/inventories/{mtag}/notepads # Tasks of an item
GET /api/v2/customers/{ktag}/notepads # Tasks of a customer
filter[type]=task returns only tasks (without a repair link);
filter[type]=maintenance_reminder returns only maintenance reminders.
Relationship to the Notebook¶
The Notebook is not a separate data foundation but a filtered view of the same notepad entries in the context of an inventory item. A free-form note is technically a task without assignment and without a due date.
Permissions¶
| Permission | Description |
|---|---|
notepad_view |
Read tasks |
notepad_edit |
Create and edit tasks |
notepad_delete |
Delete tasks |
notepad_global |
See all tasks — without it, only tasks a user created, is assigned to (directly or via group) or is listed as an additional recipient of are visible (V1 behaviour) |
E-Mail Notification¶
When the e-mail notification option (send_email) is active on create or
update, the linked contact (falling back to the customer via the configured
customer e-mail field), the assigned user and the additional recipients are
notified by e-mail (templates task_create / task_update). Updates only
trigger an e-mail when something actually changed.