FAQ
Iskue FAQ: questions, answered
The things teams usually ask before a demo. Something missing? Ask us directly.
Is Iskue really self-hosted?
Yes. Iskue runs entirely on your own infrastructure with Docker — a single host for most teams, or a distributed PostgreSQL (Citus) cluster when you need to scale out. Your tickets, attachments and user data never leave servers you control — unless you switch on an integration that sends data out, such as AI, Slack or Teams, all of which are off by default.
Read more: Deployment · Install guide
Can we migrate from Jira?
Yes. An admin-only importer, switched on with a feature flag, connects directly to Jira Cloud or Jira Data Center and brings over projects, issues, comments and attachments; re-running it is safe. We measured it on the public Apache SPARK project: 3,000 issues, 10,049 comments and 1,024 users with 0 errors. Without a connection, Iskue imports a Jira CSV export (headers such as Summary, Issue Type and Story Points are recognised) and exports CSV the same way. The migration guide lists what maps and what does not.
Read more: Migrating from Jira · Integrations
Is Iskue an alternative to Jira Data Center?
For teams that want to keep their tracker on their own servers, yes. Atlassian has announced that Jira Software, Jira Service Management and Confluence Data Center reach end of life on March 28, 2029, and new customers have not been able to buy Data Center subscriptions since March 30, 2026. Iskue runs on your own infrastructure with Docker, on one host or a Citus cluster, and its importer brings projects, issues, comments and attachments straight over from Jira Data Center or Jira Cloud.
Read more: Atlassian: Data Center end of life · Migrating from Jira
Does Iskue support single sign-on?
Yes — optional OIDC single sign-on with Google and Microsoft (Azure AD). Existing accounts link on a provider-verified email; whether SSO may create new accounts is your call — by default it follows the self-registration flag, it can be forced on or off, and an allowed-email-domains list restricts provisioning to your organisation. Local accounts can additionally enable TOTP two-factor authentication with single-use recovery codes. Without an SSO provider configured, the app simply stays password-only.
Read more: Security · Single sign-on setup
How does search work?
Iskue has TQL, a ticket query language: for example, project = CORE AND assignee = me AND status != Done ORDER BY priority DESC. It supports AND/OR/NOT, IN lists and ~ full-text contains backed by PostgreSQL, plus saved private and shared filters and an instant quick search. Results can open as an editable spreadsheet across projects, with bulk edits reported per ticket. All results respect project membership and ticket visibility.
Read more: Try TQL live · TQL reference
Can Iskue talk to our other tools?
Yes. There is a full REST API with OpenAPI documentation, outbound webhooks signed with HMAC-SHA256 and delivered through an outbox with retries, two-way Slack (raise and follow tickets from a channel) and Microsoft Teams notifications, and inbound Git integration that links commits to tickets by key reference.
Read more: Integrations · API & webhooks
Is Iskue an alternative to Jira Service Management?
For most service desks, yes. Iskue covers request types with conditional forms, a branded customer portal and help centre, customers, participants and organizations, queues with bulk actions, SLAs with pause conditions, goals and calendars, multi-stage approvals (including customer approvers, by portal or email), an email channel, a knowledge base on the portal, CSAT, two-way Slack and Microsoft Teams notifications, and ITSM: incidents, changes, problems, services, assets-lite and a public status page. It runs on the same tickets, workflows and query language as your software projects, on your own servers. AI answers are available too, with your own provider key, and stay off until you add one. Tell us how your desk works and we'll show you where it fits — and where it doesn't yet.
Read more: Service desk · ITSM · Service desk guide
Can Iskue replace Confluence?
For a lot of team documentation, yes: Docs spaces and project wikis give you a page tree, revision history, permanent links, a visual editor and 30 blocks covering most everyday Confluence macros — callouts, panels, columns, expand, table of contents, page tree, include page, child pages, status, page properties, and live ticket lists and charts driven by TQL. Some things are still missing: page attachments, page labels and page templates (with the blocks that depend on them), page watches and inline comments. HTML and RSS macros are left out on purpose, for security; imported HTML artifacts render in a sandbox instead.
Read more: Docs & wiki · Docs & wiki guide
Does the licence key phone home?
No. A licence key is a signed text string carrying your organisation name, edition, seat count and expiry date. Iskue verifies the signature locally against a public key, so an air-gapped server is licensed exactly like any other. Nothing is reported back, ever.
What languages does the interface support?
English and French, throughout the entire application.
How do we get Iskue?
Use the contact form or write to contact@iskue.com for a demo, a pilot on your infrastructure, licensing and support.
See Iskue on your own screen
A demo takes half an hour. A pilot runs on your servers, with your data, from day one.