Reference & Data Model
Task comment (task_comment) and task subscriber (task_subscriber)
Tasks have the same comment and subscriber mechanism as issues, with a stricter delete rule.
Purpose
Section titled “Purpose”Tasks from the work plan (Task) are worked on in work management. There, comments serve coordination and communication with a delegated agent; subscribers follow the task. (Data type: work data, transactional data)
Where in the app
Section titled “Where in the app”Task detail (Workmanagement › Aufgaben (Tasks) or Meine Aufgaben (My tasks) › task) › „Kommentare“ / „Aktivität“ and the „Abonnenten“ popover. See Guides › Tasks, Guides › My tasks.
Fields
Section titled “Fields”Task comment (task_comment):
| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Message | body |
Text | yes | Content | Markdown; „Bearbeiten“, „Antwort hinterlegen“, „Löschen“ |
| Reply to | parent_id |
Reference (comment) | no | Parent comment | one level |
| Author | created_by |
Reference (user) | – | Displayed with avatar and name | System |
Not in the interface: resolved_at.
Task subscriber (task_subscriber): pure mapping task ↔ user, without fields of its own; selection as with issues (without the system account, Polaris, deactivated users; agents not selectable).
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
Comment → Task (task) |
belongs to | yes | archived along | deleted along |
Comment → Parent comment (task_comment) |
belongs to | no | kept | kept |
Subscriber → Task (task) |
belongs to | yes | archived along | deleted along |
Subscriber → User (app_user) |
belongs to | yes | – | deleted along |
States
Section titled “States”None.
Rules & automation
Section titled “Rules & automation”None.
See also
Section titled “See also”Task · Issue comment · User