Features

Everything a tracker should do

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.

All features

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-123 stay unique and gap-minimal, even under concurrent creation.

…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 — replayed from the status change history against the tickets' current points, so renaming a status or a ticket mid-sprint never corrupts the chart.
  • Velocity & roadmap — completed story points per sprint, 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.
Burndown — Sprint 14
34170Day 1Day 10
Velocity — completed points, last 5 sprints
3137404347S10S11S12S13S14

A service desk, not an afterthought

Support work has different rules than sprint work. Iskue ships them in the same product. More on the service desk.

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.

A portal and a knowledge base

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.

Approvals and CSAT

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.

Email channel

Up to ten intake addresses per project, attachments and CC participants, with loop and auto-reply protection.

ITSM and a status page

Incidents, changes, problems, services and assets — and a public status page. More on ITSM.

AI, off until you say so

Portal answers, reply drafts and plain-language search with your own key. More on AI.

Docs and plans beside the work

Write the documentation and shape the portfolio in the same place the tickets live — and let both stay current on their own.

Pages with live ticket blocks

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.

Structures

Named ticket trees built from TQL, children, groups, filters and sorts, shared with View, Edit, Edit generators or Control rights. More on structures.

A sheet that writes back

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.

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. 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.

Made to fit your toolchain

More on integrations and administration.

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 · Teams

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.

Git

Commits reference a ticket key, Iskue links them to the ticket — with GitHub HMAC-signature or token auth.

Jira import · CSV

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.

Email

Optional SMTP notifications with per-user opt-out, and a service-desk email channel that turns mail into requests.

Personal access tokens

Named isk_ tokens with optional expiry for scripts, CI and assistants. Shown once, stored hashed, revocable instantly — and they act as you, never more.

When one team becomes many

The same tickets, seen from further up: cross-project plans and goals in the Professional edition, the full scaled-agile suite in Enterprise.

Professional

Plans, goals & docs

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.

Enterprise

Scaled agile (SAFe)

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.

See Iskue on your own screen

A demo takes half an hour. A pilot runs on your servers, with your data, from day one.