Features · Tickets

Tickets with real structure

Epics, stories, tasks and bugs — with sub-tickets, rollup, history and keys that never collide.

Every edition

Included from the Standard edition up. Compare editions

Tickets are the unit of work: epics, stories, tasks and bugs, each with a stable key like PROJ-123. Break anything into sub-tickets and progress rolls up to the parent — done counts and story points both. Labels, watchers, story-point estimates and a full change history are built in, and sensitive tickets can be restricted to the people who actually need to see them.

Epics, stories, tasks, bugs, sub-tasks8 custom field types4 seeded resolutions404 for restricted tickets

What you get

  • A typed hierarchy of work — epics, stories, tasks and bugs, backed by a per-project type catalogue; a parent link is only accepted when the parent's type sits higher in the hierarchy.
  • Progress that rolls up — sub-tickets report done counts and story points to their parent, and an epics view shows completion for every epic in the project.
  • Comments with guard-rails — @mentions notify project members, only the author can edit their own comment, and deleting someone else's requires a separate permission from deleting your own.
  • Complete change history — every edit is recorded with the actor, the old value and the new — status moves, reassignments, priority, estimates, due dates — and the same rows feed a project activity feed.
  • Race-safe ticket keys — sequential PROJ-123 numbers are allocated under a pessimistic database lock, so simultaneous creates never produce a duplicate key.
  • Restricted-ticket visibility — mark a ticket restricted and its content is readable only by the reporter, the assignee and admins — everyone else gets a 404, and the ticket drops out of lists and search.

Keys that never collide

Every ticket gets a key like PROJ-123, numbered sequentially per project. The number is allocated while holding a pessimistic lock on the project row, so two people creating tickets in the same instant cannot receive the same key. Uniqueness is enforced in the application layer, which keeps keys reliable even when the database is distributed across nodes.

Restricted without leaking

A restricted ticket's content — title, description, comments, history, worklogs — is visible only to its reporter, its assignee, project admins and global admins. Everyone else receives a 404 rather than a 403, so the ticket's existence is never confirmed by an error code, and restricted tickets are filtered from lists, search results and content-bearing report rows.

A history you can audit

Each field change writes its own history row: who made it, which field, the old value and the new one. Status transitions, reassignments, priority and estimate changes, due dates and comment excerpts all land in one per-ticket timeline, and the same records power a project-wide activity feed.

Resolution: the closure axis, separate from status

Status says where a ticket is in your workflow; resolution says how it ended. Each project carries its own resolution catalogue — seeded with Done, Won't Do, Duplicate and Cannot Reproduce, editable from there — and a ticket's resolution is set independently of its status, exactly the way Jira users expect. A ticket closed as Duplicate and one closed as Done can sit in the same Closed column and still report differently.

And also

The small things that make a tracker pleasant to live in, all included.

  • Planning poker — estimate a ticket with the 1-2-3-5-8-13-21 deck; votes stay hidden until someone reveals, and the round can be cleared for a re-vote.
  • Checklists and acceptance criteria — ordered items on the ticket, editable and reorderable — and any item converts into a sub-ticket with one action.
  • Co-assignees — one assignee owns the ticket; co-assignees share the work and show up on it.
  • Votes — members vote on tickets they care about, so the backlog shows demand, not just opinion.
  • Clone — duplicate a ticket within its project — type, title, description, priority, estimate and labels — with a "clones" link back to the original.
  • Move to another project — the ticket keeps its identity, so comments, worklogs, attachments and history travel with it; it receives a new key, type, status and rank, and project-specific fields are cleared with a changelog entry.
  • Due-date calendar — a month view that places tickets on their due date, coloured by priority, with a Today button.
  • Presence — see who else has the ticket open right now — a heartbeat that works across backend nodes.
  • Conflict review on saves — never lose a colleague's change: a save based on an outdated view is refused, and you review the merge, take theirs or keep yours.
  • Favourites — star a ticket and find it again from your own list.
  • Recurring ticket templates — per-project templates that create a ticket daily, weekly or monthly — claimed with a compare-and-set so a multi-node deployment never creates it twice.
Built to be operated by everyone. Board cards carry a per-card status control, so status changes work from the keyboard and on touch screens, not only by dragging. Dialogs trap focus, close on Escape and return focus to where you were. Tap targets grow to 44px on coarse pointers. Each person picks light, dark or system theme and a comfortable or compact density, and the whole interface — every label, every message — is available in English and French, remembered per user.

See Iskue on your own screen

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