Ticket Management¶

Issues sit at the heart of Kiket. They carry workflow state, metadata, and automation context defined in your repositories.

Core Concepts¶

Workflow-backed state – Each issue references a workflow, state, and transition history. States come directly from .kiket/workflows/*.yaml.
Properties – Title, description, priority, labels, story points, hierarchy (parent/root IDs), and custom fields (configured via project.yaml or extension APIs).
Assignments & roles – Assignment automation lives in workflow actions, while team roles come from team.yaml.
Activity timeline – Kiket records transitions, comments, attachments, and extension interactions for auditing.

Use the web UI, REST API, or CLI (kiket issues:create).
Reusable templates live in .kiket/templates/issues/*.yaml; sync exposes them in the UI with defaults, helper text, enforced requirements, versioned schemas (model_version), and typed custom fields.
Templates prefill type, status, priority, and custom guidance while respecting manual edits.
Validation ensures required fields defined in YAML are supplied.

Drag issues across board columns. The frontend calls the workflow executor, which validates transitions and triggers actions.
Use bulk operations to update labels or assignees—these map to API endpoints for automation.
Subscribe to issues to receive notifications or integrate with extensions to push updates to external systems.

Pre- and post-transition hooks defined in YAML run custom actions (HTTP calls, scripts, AI prompts).
Extensions can listen for issue.created, issue.updated, and issue.transitioned events.
DSAL queries aggregate issue metrics for dashboards and alerts.

Issues stay in sync with your code repositories and reflect the workflow logic you define, giving teams a single source of truth for execution.