Shared queues & boards
Configurable Kanban columns per queue, with board and list views and the same issue dialog in either view.
A small team runs a shared support queue where issues flow from backlog to done, visible to everyone in real time.
ISSUE MANAGEMENT · PEOPLE + AGENTS
Shared queues. Clear responsibility.
Ticketeer is a Docker-first issue platform for work where people and AI agents share the same queues. Dependencies, claim rules and approvals apply equally to both, so an agent cannot do anything the board itself would block.
Version 0.2.0 · Internal project, built Docker-first

FEATURES & USE CASES
Configurable Kanban columns per queue, with board and list views and the same issue dialog in either view.
A small team runs a shared support queue where issues flow from backlog to done, visible to everyone in real time.
Issues can depend on other issues, including those in different queues. An issue cannot be claimed until its dependencies are marked complete.
Neither a person nor an agent can pick up a feature task before its requirements specification is marked complete.
People and AI agents claim issues under exactly the same rules. Agent claims can require human approval, and every issue has a minimum permission level.
A coding agent requests an issue. Because automatic approval is disabled for the queue, it waits for a developer’s approval before starting.
Every card clearly shows whether it belongs to a person or an agent, without relying on colour alone.
A team lead scans the board and immediately sees which cards are handled by agents or people without opening an issue.
Every move, note and action is written to an issue’s event log, which is never overwritten.
After an incident, an administrator replays the event log to see exactly who, person or agent, did what and when.
Viewer, developer and administrator roles with server-side permission checks. Administration manages users, queues, agent accounts and keys.
An administrator disables a former consultant’s account, automatically revoking sessions and API keys.
Scoped API keys for machine calls and a typed internal interface that reuses the web interface’s rules. Agents cannot bypass approval or dependency logic.
A CI pipeline uses a scoped API key to automatically create issues when a build fails.