Tickets with real structure
Epics, stories, tasks and bugs with sub-tickets and automatic progress rollup. Labels, watchers, story-point estimates, comments and a full change history — under race-safe sequential keys like PROJ-123.
Issue tracking & agile planning
Plan, track and ship — on infrastructure you own
Iskue gives your team kanban boards, sprints, a real workflow engine, a service desk with SLAs and a query language people actually use — self-hosted with Docker, backed by PostgreSQL, with every byte of your data on your own servers.
English & French interface · your data never leaves your servers
8custom field types
38backend modules
130+end-to-end tests
EN·FRfull bilingual UI
Everything a tracker should do.
Nothing it shouldn't.
Iskue covers the full life of a ticket — from backlog to board to release — without plugins-for-basics or per-seat surprises.
Custom fields
Eight field types you define per project, stored natively in PostgreSQL — capture what your process needs without schema surgery.
A workflow engine, not a status list
Per-project statuses and transition rules, editable in settings. Start from Scrum, Kanban, bug-tracking or SAFe-portfolio templates; every transition is validated against the rules you set.
Boards that stay live
Drag-and-drop kanban with instant updates streamed over Server-Sent Events — when a teammate moves a card, you see it move.
Backlog & sprints
Precise, stable backlog ordering, one active sprint per project by design, and unfinished work that returns to the backlog when the sprint closes — automatically.
Reports you can trust
History-based burndown that survives ticket renames, velocity across sprints, a sprint roadmap timeline, and a personal dashboard of your open work across every project.
TQL search
A ticket query language with AND/OR/NOT,IN lists and full-text ~ matching — plus saved private and shared filters, and instant quick search.
Notifications, your way
An in-app inbox with an unread badge, a per-project activity feed, and an optional email channel every user can switch off for themselves.
Service desk built in
A per-project knowledge base with drafts and search, CSAT ratings on resolved tickets, and SLA policies with live response and resolution timers on every ticket.
Automation rules
When a ticket is created, updated, transitioned, commented or relabelled — and your conditions match — assign it, set priority, transition it, label it or comment. Rules run after commit and respect your workflow.
Plays well with others
A REST API with OpenAPI docs, HMAC-signed webhooks with retries, Slack activity feeds, Git commit linking by ticket key, and Jira-compatible CSV import and export.
Administration that scales
Global and per-project roles, user management with a last-admin guard, an audit log of what changed and who changed it, and built-in rate limiting.
Ask your tracker a real question
TQL — the Ticket Query Language — reads the way you think, with full-text matching backed by PostgreSQL.
project = CORE AND assignee = me AND status != Done ORDER BY priority DESCYour servers. Your data. One command.
A single Docker Compose command brings up the full stack. When one box stops being enough, the same application deploys onto a distributed PostgreSQL (Citus) cluster.
# configure secrets
$ cp .env.example .env
# full stack, one host
$ docker compose --profile full up -d
iskue ready → http://localhost:8088See Iskue on your own screen
A demo takes half an hour. A pilot runs on your servers, with your data, from day one.