SLA policies
Response and resolution targets per priority. Every ticket carries live timers for first response and resolution, with derived breach status shown right on the ticket — and the assignee is notified once when a target is breached.
Features
Everything a tracker should do
The full life of a ticket — from backlog to board to release. Every capability below ships in the core product; nothing here is a paid add-on or a plugin you have to hunt down.
Tickets and workflow, your way
Epics, stories, tasks and bugs — with sub-tickets, progress rollup, labels, watchers, story points, eight custom field types and a full change history. And underneath: a per-project workflow engine.
- Statuses you define — each project gets its own statuses and transition rules, editable in project settings.
- Templates to start fast — Scrum, Kanban, bug tracking or SAFe portfolio, then adjust freely.
- Validated transitions — every move a user (or an automation rule) makes is checked against your workflow.
- Race-safe keys — sequential ticket numbers like
PROJ-123stay unique and gap-minimal, even under concurrent creation.
To do→In progress→In review→Done
…or five statuses, or nine — with exactly the transitions your team allows.
Sprints that keep their promises
Iskue's agile tooling is opinionated where it helps and flexible where it matters.
- One active sprint per project — a guard, not a convention, so "which sprint are we in?" always has one answer.
- Backlog ordering that holds — put any ticket exactly where it belongs; ordering is stored as ranked positions and rebalanced nightly, so it never degrades.
- Rename-proof burndown — computed from ticket history, so editing titles or estimates mid-sprint doesn't rewrite the past.
- Velocity & roadmap — committed-versus-done across sprints, and a timeline view of where the work is heading.
- Your day, one page — a personal dashboard of open work by status and by project, across everything you're part of.
Try TQL — right here
This playground runs a miniature of Iskue's query engine on demo data, entirely in your browser. Edit the query or click an example: AND / OR / NOT, IN lists, full-text ~ and ORDER BY all work.
2 tickets — demo data, queried live in your browser
| Key | Title | Status | Priority | Assignee | Pts |
|---|---|---|---|---|---|
| CORE-201 | Bug: Connection timeout on webhook retry | In progress | Highest | me | 5 |
| CORE-195 | Bug: SLA timer drift on daylight saving | In review | High | me | 3 |
Saved filters
Keep queries private or share them with the team.
Quick search
Instant results as you type, from anywhere in the app.
Always scoped
Results respect project membership and ticket visibility — for every user, on every surface.
A service desk, not an afterthought
Support work has different rules than sprint work. Iskue ships them in the same product.
Knowledge base
Per-project markdown articles with draft and published states and built-in search — so the answer gets written once and found often, by your team and your reporters alike.
CSAT
Reporters rate resolved tickets from 1 to 5. You get the per-project average, the full distribution, and a reports breakdown — signal, not anecdotes.
Automation without a scripting degree
Per-project rules: a trigger, your conditions, one or more actions. Rules run after the change commits, and any transition they make is validated by your workflow — automation can't break the rules people follow.
WHENStatus changed
IFtype = Bugpriority = High
THENAssign → QA leadAdd label “regression”
Triggers: ticket created · ticket updated · status changed · assignee changed · comment added · label added. Conditions on type, priority, status, label and due date. Actions: assign, set priority, transition, add label, add comment, add canned comment.
Made to fit your toolchain
REST API
Everything the UI does, over HTTP — with OpenAPI docs served by the app itself.
Webhooks
Outbound events signed with HMAC-SHA256, delivered through an outbox with retries and a delivery log.
Slack
Per-project incoming webhook posts ticket activity straight to the channel that cares.
Git
Commits reference a ticket key, Iskue links them to the ticket — with GitHub HMAC-signature or token auth.
CSV · Jira import
Import from a Jira CSV export, export your own data the same way. No lock-in, in either direction.
Optional SMTP notification channel, off by default, with per-user opt-out.
See Iskue on your own screen
A demo takes half an hour. A pilot runs on your servers, with your data, from day one.