Entity · task_comments

Task Comment Schema

Schema-ID

task_comment

Collection

task_comments

Permissions

Lesentask_comment_view
Anlegentask_comment_create
Änderntask_comment_edit
Löschentask_comment_delete

Felder

Task Comment Schema

task_comments4 Permissions

Threaded comment on a task

taskIduuiderforderlich

Reference to task

projectIduuidoptional

Project ID for scoping queries

parentCommentIduuidoptional

Parent comment ID for threaded replies

nullable

bodystringerforderlich

Comment text (may contain @mentions as @[userId])

1–5000 Zeichen

mentionsuuid[]optional

User IDs mentioned in this comment

Default: []

isResolvedbooleanoptional

Whether this comment thread is resolved

Default: false

resolvedByuuidoptional

Who resolved this thread

read-onlynullable

resolvedAtdatetimeoptional

read-onlynullable

sourcestringoptional

Where the comment came from (INTERNAL = team member, CUSTOMER = customer portal).

Werte

INTERNALCUSTOMER

Default: "INTERNAL"

authorPartyIduuidoptional

Customer party (set for CUSTOMER-source comments).

nullable

reactionsobject[]optional

Emoji reactions (Teams-style). Managed exclusively via POST /:resource/:id/reactions — never set directly via create/update (the field is protected). Absent/missing = no reactions.

read-only

emojistringerforderlich

Native Unicode emoji character

1–32 Zeichen

userIdstringerforderlich

Internal users._id of the reactor

min 1 Zeichen

createdAtdatetimeoptional

When the reaction was added

read-only

Standard-Endpoints

Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:

GET /api/v1/task_comments — Liste, paginiert + filterbar
GET /api/v1/task_comments/<id> — Einzelne Entity
POST /api/v1/task_comments — Anlegen
PATCH /api/v1/task_comments/<id> — Teil-Update
DELETE /api/v1/task_comments/<id> — Soft-Delete
GET /api/v1/task_comments/<id>/timeline — Audit + Aktivitäten