Configuration reference

Reference for every setting on the admin and project settings pages. All configuration is stored in Forge storage for your site — see Security for how it's protected.

Who can configure what

Connecting Sentry — entering the organization slug, base URL, client secret and auth token — is limited to Jira admins, on the admin page (Jira settings → Apps → Autoticket). Mapping an individual Sentry project to a Jira project is limited to project admins for that project, on that project's Project settings → Autoticket page.

Connection settings (admin page)

• Sentry organization slug — the part after sentry.io/organizations/ in your Sentry URL.
• Sentry base URL — https://sentry.io, or a regional host such as https://de.sentry.io.
• Client secret / Auth token — from your Sentry internal integration. Stored in Forge's encrypted secret storage, never shown again after saving.
• AI summaries — off by default; see AI summaries below.

Project mapping (project settings page)

• Sentry project slug(s) — which Sentry project(s) feed this Jira project.
• Issue type and optional default priority for created work items.
• Create mode — every new Sentry issue, or only alert rules (see the setup guide's alert-rule step).
• Environment allowlist and minimum level — optional creation filters. Filtered events are logged in the activity log with the reason, never silently dropped.
• Dedupe rule — one work item per Sentry issue, or one per issue and environment.
• Reopen on regression — whether a Sentry regression reopens the existing work item (with a comment) instead of leaving it closed.
• Sentry panel — show or hide the status panel on linked work items.

Content templates

Available tokens: {{title}}, {{environment}}, {{release}}, {{level}}, {{url}}, {{count}}.

• Summary template — shapes the Jira work item's title, for example [{{environment}}] {{title}}.
• Labels — tokenized and sanitized to Jira-safe label syntax.
• Priority by level — maps Sentry's level to a Jira priority, for example fatal=Highest, error=High (names or ids).
• Required custom fields — one line per field, such as customfield_10051={{environment}}. This is the one thing Sentry's own Jira integration can't do on any Sentry plan.

AI summaries

Off by default, enabled per site by a Jira admin. When on, Atlassian-hosted Forge LLMs add a one-sentence summary, a likely cause, and a suggested code area to the work item description — never an assigned person. There's no third-party AI vendor key to configure, and no extra network egress. Usage is capped per site per UTC day; once the cap is reached, the work item is still created, with the description noting the summary was skipped.

Setup guide · FAQ