Getting started with KAMI Tasks
KAMI Tasks is KAMI's project and work management module: tickets, sprints, boards and reports for any team's work — development, HR, operations or anything else. This article is a tour of the main screens so you know where everything lives.
Who can use it
Everyone in your company who has been given access. The people you see in KAMI Tasks come from your main KAMI account — users are added or removed under My Teams › Profile › Access settings, not inside Tasks itself.
The pieces, in one paragraph
Work is recorded as tickets. Tickets belong to a project, which gives them a key like KDV-123. Tickets are planned into sprints — short, fixed periods of work — and grouped under epics for larger initiatives. You work your sprint from the Kanban board or the List, watch your own workload on My Work, and read how the sprint went in Insights.
The main screens
| Screen | What it is for |
|---|---|
| My Work | Your personal landing page — what needs your attention today |
| Kanban | The sprint board: tickets as cards in status columns |
| Timeline | Work laid out over time, with releases and dependencies |
| List | Every ticket as a table — filter, group, and bulk edit |
| Projects | The projects in your company, and their settings |
| Sprints | The Sprint Manager: create sprints and move them through their lifecycle |
| Users and Groups | Who is here, and how they are organised into teams |
| Templates | Reusable tickets you can drop into any sprint |
| Notifications | Everything that happened that involves you |
| Timelog | Time logged across the company |
| Insights | Sprint reporting: progress, velocity, workload |
| KAMI PM | Your AI project manager — see KAMI PM, your AI project manager |
| Settings | Projects, automations, ticket standards, integrations and import |
Where to start
- Check My Work each morning — it collects what is overdue, due today, due this week and blocked, plus your sprint progress. See My Work: your daily view.
- Work the board during the day — drag tickets between columns as they progress. See The Kanban board.
- Log your time on tickets as you go, so estimates and reports mean something. See Estimates and logging time.
For the person setting KAMI Tasks up
Do these once, in this order:
- Create a project — its slug becomes the prefix of every ticket key. See Projects and access.
- Organise people into groups and give the groups access to the project. See Users and groups.
- Create your first sprint and set its dates and goal. See Sprints.
- Optionally set ticket standards so every ticket is written the same way — and KAMI AI can fix stragglers with one click. See Ticket Standards.