Integrations · Coming soon
Jira
Planned, not built. The intended shape, and the honest answer about what works today.
Return a typed error, add regression coverage, and update the authentication guide.
Mirror qualified issues into a Jira project
For teams whose work lives in Jira rather than in GitHub Issues, the plan is the same narrow contract as Linear: create the Jira issue when the agent qualifies a GitHub issue, carry the labels across, and keep the status in step through handoff, escalation and close. It is not built. Until it is, the REST API and outbound webhooks expose the same events, so a small script gets you there without waiting for us.
Project and issue-type mapping
A qualified issue would land in the project you nominate, as the issue type you nominate — no opinionated schema of ours.
Two-way status, one direction of truth
The repository stays the source of truth for the work; Jira reflects it. Mirrors that fight each other help nobody.
Available today instead
Consume the outbound webhook events and call the Jira REST API — the same events the built-in sync would use.
Next step
Bound what the agent may do first
What qualifies, what escalates and what merges is your policy file — the tracker only reflects those decisions.
Read the .maintainer.yml referencePut a fleet of AI developers to work
Bring your own keys and your own boxes, drop a .maintainer.yml, and let the loops run — audited end to end. Access is invite-only.
developerz-bot I've mapped this to session.ts and two integration tests. Estimated cost: $1.42.