Tasks Module

The Tasks module manages cross-workspace tasks. Source: packages/server/src/modules/tasks/.

REST Endpoints

All endpoints are prefixed with /api/v1/tasks and require ClerkAuthGuard.

Filters for GET /tasks

Visibility

A task is visible only to its creator and, once assigned, its assignee — both parties to an assignment can see it, nobody else can. GET /tasks and GET /tasks/:id only ever return tasks the caller is one of those two parties to. This applies to every org role, including OWNER/ADMIN — no role has elevated, org-wide visibility.

List/get responses include assigneeName/creatorName (falling back to email when the user has no display name) so a client can render "Assigned by <creatorName>" for the assignee and "Assigned to <assigneeName>" for the creator.

A task outside the caller's visibility is reported as 404 Not Found (not 403) from GET /tasks/:id, so its existence isn't leaked to someone who can't see it.

Task Service (services/tasks.service.ts)

create(orgId, userId, dto)

Creates a new task. Fields:

An unassigned task (assigneeId: null) is visible only to its creator. Once assigned, it's visible to both the creator and the assignee.

update(orgId, taskId, dto)

Partial update. When status is set to DONE, completedAt is automatically set to now(). When status changes away from DONE, completedAt is cleared.

reorder(orgId, taskIds)

Accepts an ordered array of task IDs. Updates sortOrder for each task to reflect the new order. Used for drag-and-drop reordering in the Hub.

reprioritize(orgId, changes)

Applies AI-driven priority and sort order changes to multiple tasks in one call. Each change specifies:

{
  taskId: string;
  priority?: TaskPriority;
  sortOrder?: number;
  reason: string;  // required — why the AI changed the priority
}

Changes are applied sequentially via individual repository updates.

seedOnboardingTasks(orgId, userId, workspaceId?)

Creates 6 sample tasks to demonstrate the workspace functionality during onboarding. Called by POST /tasks/seed. These are created unassigned, so — per the visibility rule above — they're only visible to whoever triggered the seed, not to other org members, until assigned.

Task Status & Priority

TaskStatus

TaskPriority

Unassigned Tasks

Tasks with assigneeId = null are private to their creator (see Visibility above) until assigned. The Hub's task filter has an Unassigned view for these — it shows only the current user's own not-yet-assigned tasks, not every unassigned task in the org.