Settings

Automations

Automations are the rules that chase things so a person doesn't have to: a ticket goes blocked and someone is told, a critical ticket sits unassigned and someone is told, a sprint end approaches and…

Read article →

Importing tickets from a spreadsheet

Moving to KAMI Tasks from another tool — or from a planning spreadsheet — doesn't mean retyping the backlog. The import takes a spreadsheet and turns its rows into tickets.

Read article →

Integrations: GitLab, Slack and Claude Code

Integrations connect KAMI Tasks with your development tools so tickets stay in sync automatically — code activity lands on tickets, ticket activity lands in Slack, and an AI assistant can work your…

Read article →

Ticket Standards

Ticket Standards are your company-wide rules for how tickets are written — one format for titles, one structure for descriptions, applying to every ticket type in every project. They exist so a board…

Read article →

Users and groups

People reach KAMI Tasks through two layers: users — everyone in your organisation who can be assigned work — and groups, the teams they are organised into. Groups are what projects actually grant…

Read article →