All guides › Set up for the team
Set up for the teamJira, Linear, Slack and Teams: returned steps where the team works
File a returned step as a Jira or Linear issue with its screenshot and notes, link runs to issues by key, and send each project's events to its own Slack or Teams channel.
A reviewer returns a step at four in the afternoon. By five the note has been copied into Jira without the screenshot, and the developer asks in Slack which screen it was about. Kaloko files the issue from the step itself and tells the right channel.
The problem
Review happens in one tool, planning in another and talk in a third. Every copy between them loses something: the screenshot, the criterion, the language the bug was in. Notifications go to one busy channel where nobody reads them.
What changes with Kaloko
An admin connects Jira Cloud or Linear and the chat tools once, in Settings → Integrations, and maps Kaloko projects to Jira projects or Linear teams. From then on an issue starts from the step and comes back to it when it is done, and each project reports to the channel its team actually reads. Both come with the Team plan and up.
How it works
- Connect the tracker
in Settings → Integrations an admin connects Jira Cloud (OAuth or an API token) or Linear (OAuth or an API key) and maps each Kaloko project to a Jira project and issue type, or to a Linear team.
- File from the step
on the canvas, in review mode or with
kaloko issue create --step checkout --to jira --criterion AC2. The issue gets the screenshot, the criterion with its evidence, the reviewers' open notes and a link back to the step. - Let it come back
when the issue is done or cancelled in the tracker, the comment on the step gets a reply and is resolved; reopened, it opens again. For Jira the admin adds the webhook Kaloko shows; Kaloko also checks every 30 minutes.
- Link runs by key
a branch or pull request title that names the issue (
feat/WEB-12-gift-cards, Linear'seng-42) links the run to it, and the issue gets a comment when the run is shared. - Pick channels per project
add a Slack channel with *Add to Slack*, or a Teams channel through a Workflows URL. Each channel chooses its events (new run, returned, accepted, comment, mention, release recorded) and quiet hours; messages that arrive during quiet hours wait until they end.
Skills and prompts
File the returned checkout step of the latest TASK-123 run in Jira with the failing criterion, then tell me the issue key.Expected outcome: kaloko issue create runs once for that step and the agent answers with the key and the link. Without a connected tracker it says an admin has to set it up.
List the open Kaloko issues for the checkout scenario.Expected outcome: kaloko issue list --scenario checkout --state open with keys, steps and states.
What you get
- Issues that carry the screenshot and the criterion, so nobody asks "which screen?".
- Comments on steps that close themselves when the work is done.
- Channels that hear about their own project only. A restricted project reaches only the channels that name it.
FAQ
Do we need both Jira and Linear?
No. Connect the one you use; the CLI and the canvas offer only what is connected.
Who can file issues?
Developers and testers, on the canvas or with a token that may comment. Viewers see the issues on the steps.
Does the organization-wide Slack channel still work?
Yes. Channels per project come on top of it.