# Made to fit your toolchain

Source: https://iskue.com/features/integrations/

> REST API, signed webhooks, two-way Slack, Microsoft Teams, Git linking and Jira-compatible CSV.

Everything your team does in the tracker is reachable over a documented REST API, and every ticket event inside it can flow out — to your own endpoints, to Slack, or back onto tickets from your Git host. Outbound webhooks are signed and retried from a durable outbox. Inbound, commits and pull requests link themselves to tickets by key, CSV moves data in and out in a Jira-compatible shape, and a dedicated importer pulls whole projects from Jira Cloud or Data Center. Scripts and AI assistants authenticate with personal access tokens that act exactly as their owner.

## What you get

- **REST API with OpenAPI**: Every feature is served over a versioned REST API under /api/v1, with an interactive OpenAPI reference in the app at /api-docs.
- **Personal access tokens**: Create named isk_ tokens under Account → API tokens with an expiry of 30, 90 or 365 days or none; send one as a Bearer token and it acts as you — never more than your own permissions, narrowed to the access level you chose: read only, read & write (the default) or full. Only a hash is stored, the secret is shown once, revocation is instant and last use is tracked.
- **Signed outbound webhooks**: Register per-project webhook endpoints with an event filter; each delivery carries an HMAC-SHA256 signature in the X-IssueHub-Signature header, plus event and delivery-id headers your endpoint can verify.
- **Two-way Slack, Microsoft Teams notifications**: Raise tickets from Slack with an emoji reaction or /iskue, turn a request channel into a service-desk intake with replies synced back into the thread, and post ticket activity to Teams. The one-way Slack incoming webhook still works too.
- **Git commit and PR linking**: A per-project inbound webhook authenticates pushes by GitHub HMAC signature or a shared token header, then links commits, branches and pull requests to tickets wherever a message, branch name or PR title mentions a key like PROJ-12.
- **Jira-compatible CSV**: Export a project's tickets as CSV, and import CSV with only a title column required — Jira export headers such as Summary, Issue Type and Story Points are recognised automatically, with per-row error reporting.
- **Direct Jira import**: An admin-only importer — off by default, enabled with one flag — connects to Jira Cloud (REST v3, API token) or Jira Data Center (REST v2, personal access token or anonymous), and imports projects, issues, comments, attachments, labels and users; rich text is normalised to Markdown and re-runs are idempotent. Proof point: a 3,000-issue Apache SPARK import with 0 errors.

## The Jira importer, measured

Set APP_JIRA_IMPORT_ENABLED=true and an admin screen appears: test the connection, pick projects, run. Cloud and Data Center differ in API version, pagination, rich-text format and authentication, and the importer handles each: Cloud over REST v3 with ADF rich text and an API token; Data Center and Server over REST v2 with wiki markup and a personal access token or anonymous access. Both are converted to Markdown. Issue types map onto yours and fall back to Task; users are provisioned; labels come across. The job runs asynchronously with its progress persisted, so status survives a restart and reads correctly behind a load balancer, and a mapping table makes a second run update rather than duplicate. Measured against the public Apache SPARK project on Jira Data Center: 3,000 issues, 10,049 comments, 1,024 users and 141 labels in 28 minutes, with 0 errors.

## Tokens that act as you, and only as you

A personal access token is the credential for anything that is not a browser: a script, a CI job, an AI assistant. It carries no separate identity — a request with your token is a request by you, checked by the same permission gates as the UI and narrowed to the access level you chose (read only, read & write or full), and it stops working the moment your account is deactivated. Tokens are prefixed isk_ so they can never be mistaken for a session, only their SHA-256 hash is stored, the secret appears exactly once at creation, and the list shows each token's prefix, expiry, last use and revocation.

## Webhook delivery you can audit

Outbound deliveries use an outbox pattern: the delivery row is written in the same transaction as the change itself, so an event is never lost to a crash. A background poller then sends pending deliveries with exponential backoff — up to five attempts, starting at 30 seconds and doubling each time — and a compare-and-swap claim guarantees exactly one node delivers even when several backends poll the same queue. A per-webhook delivery log shows the last 50 deliveries with status, attempt count and last error; the signing secret itself is never returned by the API.

## Smart commits

With Git integration enabled, a project admin can additionally opt in to Jira-style smart commits: #comment adds a comment, #time logs work (2h 30m, with w and d as working weeks and days), and any other #word is matched against your workflow's status names as a transition. Commands run as the commit author, matched by email — no matching account, no actions — and go through the same services as the UI, so permissions, workflow rules and notifications all apply.

## Sandboxed plugins

Installed plugins can carry a JavaScript script that runs in a locked-down GraalJS sandbox: no host classes, no filesystem, no network. Scripts react to three hooks — onTicketEvent, onComment and onSlaBreach — run in the background after the change is saved, and are bounded by a 100,000-statement limit, a 5-second wall-clock watchdog and a 256 MB memory budget, with at most 10 collected actions per run. They can add labels, assign, move a ticket along an allowed transition, add an internal note and set a custom field. A failing or runaway script is isolated and logged; it can never break the operation that triggered it. A marketplace installs plugins from a built-in catalogue or from catalogue sources you add, each download verified against its SHA-256 digest. A full plugin platform in the Jira Data Center model — Java plugins with their own REST endpoints, screens and storage — is planned.

## Key facts

- HMAC-SHA256 signed payloads
- 5 delivery attempts with backoff
- 3,000-issue Jira import, 0 errors
- 3 plugin hooks

## In practice

```
git commit -m "PROJ-12 #comment deployed to staging #time 2h 30m #done"

curl -H "Authorization: Bearer isk_…" https://iskue.example.com/api/v1/search/tql?query=assignee%20%3D%20me
```
