Issue Tracking
Kuayle supports the core path from issue creation through triage, assignment, planning and completion. Multiple people can be assigned to the same issue, and each team can define its own statuses.
Rich issue model
Issues include a rich-text description, priority, due date, multiple assignees, labels, comments and change history. Sub-issues appear in a tree, and relations record blocked-by, blocking, duplicate and related links.
- Multi-assignee support — no single-owner assumptions
- Sub-issues with tree view and counter badges
- Blocking/blocked, duplicate, and related issue links
- Rich text editor with code blocks, mentions, and task lists
- File uploads with S3-compatible storage
Custom statuses and workflows
Each team defines its own statuses and workflow. Move cards on the team board or press S from an open issue to choose a status. Teams in the same workspace can use different status sets.
- Per-team custom statuses
- Configurable auto-transitions via GitHub events
- Bulk issue updates from list views
Issue templates
Workspace issue templates can prefill title, description, status, priority, assignee and labels in the issue creation dialog. Templates may be limited to a specific team.
- Workspace-level template management
- Prefilled issue fields in the creation dialog
- Optional team scope
Public sharing
Create token-based, read-only links scoped to a workspace, team, project or saved view. Recipients can browse the issues exposed by that scope without a Kuayle account.
- Workspace, team, project and view scopes
- Optional expiry and description visibility
- No account required to open the link
Review Kuayle before you deploy it
Inspect the Apache 2.0 source, then follow the Docker Compose guide to run an instance on your infrastructure.