Overview
Kanban with git integration: cards git moves
Kanban with git integration instead of hand-updating: commits, pull requests, releases and deploy gates move the cards through your rules, and the code graph shows what shipped. In Zuuna, from the Developer plan.
A board rarely lies out of malice. It lies because its state is hand-maintained: the work merged long ago, but the card still sits in In-Progress because nobody thought of it. Kanban with git integration turns that around: the repository operates the board, not the person: commits, pull requests, releases and deploy gates are the state.
How the card moves itself
The mechanism starts in the commit: mention a card key like ZNA-2001 in the commit message or the branch name and the work links itself. A development panel appears on the card with branch, commits, pull request and build status; a marker on the board shows which cards have code.
From there, automations you define move the card: to In-Progress when a branch appears or a commit lands. To Review when a pull request opens. To Done when the pull request merges. The repository webhook reports it, nobody moves a mouse. And when the build goes red, it reads red on the card, not somewhere inside your CI tool.
Releases and the deploy gate
A release in Zuuna is bound to a real git tag. It is done because the tag exists, not because someone coloured a row green. The deploy gate only flips when your pipeline reports it; you approve at the board. What shipped and when then sits on a timeline: release after release as a band across the board history.
The code graph: what shipped without a ticket
A board derived from git can also show what never had a card: the code graph lists open branches and every commit that went out without a card key. Exactly the gap hand-driven boards are blind to becomes visible.
Hand-maintained versus derived from git
| Hand-maintained board | Board derived from git (Zuuna) | |
|---|---|---|
| Card moves because | somebody remembered | the pull request merged |
| Release is done because | the row was marked green | the git tag exists |
| Build status | in the CI tool, if you go look | red, yellow or green on the card |
| In a dispute | "I meant to update it" | evidence right on the card |
| Work for the board | daily, by everyone | none |
When coding agents operate the cards
In the agent era this stops being a nice feature and becomes the core: a coding agent reads the card over the Zuuna MCP server (mcp-server-zuuna on npm), builds in your repository with its own tools (Claude Code, Cursor, Codex) and when the pull request merges, one of your rules moves the card. Nobody drags cards for agents. Setting the loop up: Zuuna for AI agents. Why nobody can lie to a board derived from git is in the blog post: The board can't lie when agents write the code.
Setup: one script, any git host
A script goes into your repository: it reports commits to Zuuna using an API token, with no OAuth app and no bot account. That works with any git host: GitHub, GitLab, Gitea, including an instance reachable only inside your network. Automatic pull-request tracking runs over the repository webhook; GitHub is the best supported there, more hosts are following. Step by step: link commits to cards automatically and move cards automatically with git.
The git integration is included in the Developer plan: €24 incl. VAT per seat and month (€20.17 net plus VAT for companies), with a 14-day trial and no credit card. The code graph and releases are included.
See the live demo: a real Zuuna board moved by real commits. Coming from Jira, Trello, Asana or Excel? Add the free migration.
FAQ
Which plan includes the git integration?
The Developer plan: €24 incl. VAT per seat and month (€20.17 net plus VAT), free to try for 14 days without a credit card. The code graph and releases are included.
Does it work with GitHub, GitLab and Gitea?
The commit hook and the CLI work with any git host, including a self-hosted instance on your own network. For automatic pull-request tracking you connect the repository webhook; GitHub is the best supported there, more hosts are following.
Do I need an OAuth app or a bot account?
No. An API token with the scopes the script needs is enough, and can be revoked when you are done. The other way round, Zuuna does not read your repository: it receives what the script reports and never asks inside the repo.
Do only merged pull requests move cards?
No, you define the rules: card moves when a branch appears, when commits land, when a pull request opens or merges, or when the build goes red, as automations listening to git events. Without a rule, nothing moves except the evidence appearing on the card.
Can an AI agent work with this?
Yes. Over the MCP server mcp-server-zuuna (on npm), the agent reads the board and its cards and can comment on them. The code itself is written in the repo with the agent's own tools. Zuuna writes no code and makes no decisions. Details on the Zuuna for AI agents page.
Is this a Jira replacement?
For development teams that want board, git and releases in one tool: yes, that is the core of the Zuuna vs Jira comparison. A marketplace ecosystem, hundreds of custom workflows and enterprise processes Zuuna does not replace.