SLAs that pause
Named SLAs with start, pause and stop conditions, goals chosen by TQL and business-hour calendars. Timers show on the ticket, in queues and on the portal, and every breach is notified exactly once.
Features
The full life of a ticket — from backlog to board to release. Everything on this page is part of one product in three editions: the core tracker is Standard; cross-project plans, goals, dashboards, docs spaces and the customer portal are Professional; the scaled-agile suite, custom roles, plugins and email-template overrides are Enterprise. Every detail page says which — no plugin marketplace to hunt through.
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.
PROJ-123 stay unique and gap-minimal, even under concurrent creation.More on tickets, custom fields and the workflow engine.
…or five statuses, or nine — with exactly the transitions your team allows.
Iskue's agile tooling is opinionated where it helps and flexible where it matters.
More on boards, backlog & sprints, reports and notifications.
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.
| 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 |
Any result set opens as a sheet across projects: cells edit in place, custom fields become columns, status cells offer only the transitions your workflow allows, and bulk edits report a result per ticket. Try it — edit a cell, select a few rows, save.
| Select | Key | Project | Title | Status | Priority | Assignee | cf["Severity"] |
|---|---|---|---|---|---|---|---|
| CORE-201 | CORE | ||||||
| CORE-195 | CORE | ||||||
| SUP-418 | SUP | — | |||||
| SUP-402 | SUP | — | |||||
| CORE-179 | CORE |
Keep queries and sheet layouts private or share them with the team.
Instant results as you type, from anywhere in the app.
Results respect project membership and ticket visibility — for every user, on every surface. More on TQL.
Support work has different rules than sprint work. Iskue ships them in the same product. More on the service desk.
Named SLAs with start, pause and stop conditions, goals chosen by TQL and business-hour calendars. Timers show on the ticket, in queues and on the portal, and every breach is notified exactly once.
Request types with conditional forms, a branded portal and help centre, participants and organizations — plus the articles you choose to publish, suggested while customers type, so the answer gets written once and found often.
Approval steps on any status — users, groups or customers, with all, any, quorum or percentage rules, in the app, on the portal or by email. When it's done, customers rate the resolution from 1 to 5.
Up to ten intake addresses per project, attachments and CC participants, with loop and auto-reply protection.
Incidents, changes, problems, services and assets — and a public status page. More on ITSM.
Portal answers, reply drafts and plain-language search with your own key. More on AI.
Write the documentation and shape the portfolio in the same place the tickets live — and let both stay current on their own.
Docs spaces and project wikis with a visual editor and 30 blocks: callouts, columns, page trees, includes — and TQL ticket lists and charts that every reader sees through their own permissions. More on Docs.
Named ticket trees built from TQL, children, groups, filters and sorts, shared with View, Edit, Edit generators or Control rights. More on structures.
Quick-filter and quick-group chips, saved views shared with Use, Update and Manage tiers, and Σ or formula columns copied back into ticket fields — previewed first and revertible.
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. More on automation.
Triggers: ticket created · updated · status changed · assignee changed · comment added · label added · customer or public reply · request type or field changed · SLA threshold · approvals · TQL match · incoming webhook · cron. Conditions on type, priority, status, label, due date, custom fields or any TQL query. Actions: assign, set priority, transition, add label, comment or canned reply, edit a field, create a ticket, send an email, call a webhook.
More on integrations and administration.
Everything the UI does, over HTTP — with OpenAPI docs served by the app itself.
Outbound events signed with HMAC-SHA256, delivered through an outbox with retries and a delivery log.
Two-way Slack: raise tickets with a reaction or /iskue, and run a request channel with replies synced to the thread. Teams gets the activity that matters.
Commits reference a ticket key, Iskue links them to the ticket — with GitHub HMAC-signature or token auth.
A live importer pulls projects, issues, comments, attachments and users straight from Jira Cloud or Data Center (off by default, one flag to enable) — measured on a 3,000-issue Apache SPARK import with 0 errors. Jira-compatible CSV works in both directions too. Migration guide.
Optional SMTP notifications with per-user opt-out, and a service-desk email channel that turns mail into requests.
Named isk_ tokens with optional expiry for scripts, CI and assistants. Shown once, stored hashed, revocable instantly — and they act as you, never more.
The same tickets, seen from further up: cross-project plans and goals in the Professional edition, the full scaled-agile suite in Enterprise.
Cross-project Gantt plans with dependencies, capacity bands and what-if scenarios you commit or discard; goals that measure themselves from linked tickets; documentation spaces with page trees, revisions and cross-space search.
Agile Release Trains and solution trains, Program Increments with objectives, ROAM risks, burn-up and predictability, a program board with dependency arrows, value streams with lean-budget guardrails, and persona rooms for the RTE, the team and the portfolio.
A demo takes half an hour. A pilot runs on your servers, with your data, from day one.