Skip to content

Reference & Data Model

Overview

An issue is a standalone work item with a state machine, priority, due date, assignment and optional delegation to an agent.

Unlike a task, an issue has no dates in the work plan, no effort and no resources. It has a state („Entwurf“ to „Erledigt“, draft to done), a priority, a due date, an assignment to a user and a Delegate field („Delegieren“) with which Polaris or an AI agent takes over the issue. Issues can be structured into sub-issues, organized with labels and followed by subscribers. Collaboration runs through comments with replies; a delegated agent also answers via comment.

There is no selectable issue type in the interface. All issues are technically custom.

User (app_user) ◀── Assignment ─── Issue (issue) ─── Project (project, optional)
User (app_user) ◀── Delegate ─────┤ └── Department (osp_employment_unit, optional)
├── Parent issue (issue) ── Sub-issues
├── Labels (issue_label) via issue_label_map (n:m)
├── Subscribers (app_user) via issue_subscriber (n:m)
├── Comments (issue_comment) ── Replies (issue_comment)
└── Files (file_link, ch. 10)
Task (task) ── Comments (task_comment) ── Replies
└── Subscribers (app_user) via task_subscriber
Delegate set / comment to agent ──System──▶ Conversation (agent_conversation) = „Agent-Protokoll“ (ch. 11)
Entity Technical Purpose Where in the app
Issue issue Ticket with state, priority, due date, assignment, delegation Workmanagement › Allgemein › Issues, Inbox › Meine Issues, Project › „Tickets“ (Guides › Issues, Guides › My issues)
Label issue_label (+ issue_label_map) Freely definable keyword with color Issue detail › „Labels“; filter and grouping
Subscriber issue_subscriber User who follows an issue Issue detail › „Abonnenten“
Issue comment issue_comment Message or reply in the comment thread Issue detail › „Kommentare“
Task comment task_comment (+ task_subscriber) Comments and subscribers of a task Task detail › „Kommentare“ (Guides › Tasks)

Workspaces (saved views with grouping, sorting, display and filter) are not a database entity; they are stored client-side.