Jira
File a real Jira issue without leaving ForgeOps
Connect a project with an API token, then turn any issue into a real Jira issue in one click, an optional AI summary included.
- An API token from your own Atlassian account, not an OAuth app to register or get approved
- One click files the issue: title, culprit, first/last seen, event count, and the latest occurrence's backtrace, plus a link back to the ForgeOps issue
- Filing again is blocked once one exists for a given issue; the button becomes a link to the Jira issue instead of creating a duplicate
- Optional: a plain-language AI summary, suggested priority, and suggested labels added to the filed issue, Business plan and up
A token you generate yourself, scoped to your own tenant
Jira Cloud is one instance per tenant, so a Jira connection needs three fields, not two: your own instance URL (e.g. "https://yourcompany.atlassian.net"), the project key to file into (e.g. "ENG"), and an API token generated at id.atlassian.com/manage-profile/security/api-tokens, authenticated over HTTP Basic alongside the account email it belongs to.
From there, an issue's detail page gets a "Create Jira issue" button for anyone with at least member access. The request goes straight to Jira's own REST API v3, formatted as a real Atlassian Document Format description, not a plain text dump.
The same action row as Resolve/Ignore/Reopen, once a project's connected.
Optional: an AI summary, right in the filed issue
Turn on "Use AI to enrich tickets" in a project's settings and every issue filed from it gets a short, plain-language summary of what likely went wrong, plus a suggested priority and a couple of suggested labels, ahead of the usual culprit/backtrace detail. It's clearly labeled as AI-suggested text, not written into Jira's own priority or label fields.
Business plan and up, with a monthly allowance of enrichment calls per organization; a ticket still files normally, with its usual content, once that allowance runs out for the month.