Issues, comments and status changes are rows on the same substrate as your customers and projects. No separate tracker to sync, no webhook glue — and your AI agents read and triage issues with the tools they already have.
Jira, Linear and GitHub Issues live in their own world. The bug about a customer’s pod has no link to the customer. Syncing trackers to business data means webhook glue that breaks quietly.
An issue is a row that links to the customer, the invoice, the project it concerns. Comments and status changes are rows too — auditable, queryable, and readable by AI agents without any integration work.
Create, list, get, update, comment — plain HTTP endpoints. Wire them into forms, workflows or agents without an SDK.
Discussion lives on the issue as structured rows — searchable and auditable like everything else on the substrate.
Attach the customer, invoice or project the issue concerns. Walking from a complaint to the account takes one query.
Agents read and update issues through the same MCP tools they use for Tables — assign, label and close from a workflow.
Issues live in your org’s partitions. Add columns like any table — severity, SLA clock, component — without waiting on us.
Installable per organisation, gated server-side like every Elastbiz app.
The same binary. The same substrate. Move between them with a data export.
We host Issues at app.elastbiz.com. EU data residency, backups on us.
Docker one-liner. Your issues stay on your disk; the substrate handles everything else.
Issues linked to the business they concern. Comments, status, AI triage — one substrate.