VVenture VD

ErrorLink

ErrorLink documentation

ErrorLink connects one hosted Sentry organization to a Jira Cloud installation. A Jira administrator configures the connection, project mappings, and occurrence thresholds. For help, contact support@venturevd.com.

Before you begin

  • Use Jira Cloud and hosted Sentry; Jira Data Center/Server and self-hosted Sentry are not supported.
  • Have Jira-administrator access and permission to create a Sentry internal integration.
  • Create one dedicated Sentry internal integration per Jira installation. Grant only the organization/project read and issue/event administration permissions needed to list projects, receive issue/error webhooks, read issue state, and update resolved/unresolved state.
  • Enable issue lifecycle and new-error webhook actions. Store the generated API token and OAuth client secret in a password manager. The OAuth client secret, not the API token, signs webhooks.

Connect Sentry

  1. In Jira, open Apps → Manage apps → ErrorLink → Configure.
  2. Select Apply storage migrations. “Storage schema is current” is a healthy result.
  3. Enter the Sentry organization slug and internal-integration token, then select Test connection. Correct the slug, token, or Sentry permissions if the expected projects do not appear.
  4. Select only the projects you intend to connect. Enter the Sentry OAuth client secret in Webhook client secret, then select Save connection.
  5. Reload and confirm ErrorLink remains connected while neither credential is displayed. Copy the installation-specific Webhook delivery URL into the Sentry integration and save the integration again.

Treat the Webhook delivery URL as sensitive operational metadata. Never send the API token, OAuth client secret, webhook URL, signature, DSN, or raw payload to support.

Create a project mapping

  1. Choose a selected Sentry project, destination Jira project, and non-subtask Jira issue type.
  2. Set Minimum occurrences between 1 and 1,000,000. Start at 10 unless your team intentionally wants earlier issue creation.
  3. Save the mapping and confirm it appears in the active list.

A Sentry project maps to one Jira destination. Removing a mapping stops future automatic creation for that project; it does not delete existing Jira issues or ErrorLink history.

How synchronization works

When a signed webhook meets the mapping threshold, ErrorLink creates one Jira issue for the Sentry error group and records the event and processing attempts in the sync log. Retries and concurrent deliveries are deduplicated. Resolving or reopening a linked Jira issue updates Sentry; resolving or reopening in Sentry updates the Jira status category. An active paid license or evaluation is required for new sync work and configuration changes.

Safe troubleshooting

  • Connection test fails: verify the organization slug, token, least-privilege Sentry permissions, and hosted-Sentry requirement.
  • Webhook fails: confirm the OAuth client secret was entered as the webhook secret and that the saved Sentry integration uses ErrorLink's installation-specific URL.
  • No Jira issue: review the active mapping, threshold, license state, and sync-log outcome.
  • Status does not converge: confirm the Jira workflow has appropriate done/non-done status categories and the Sentry integration can administer issue state.

Send support the Jira site hostname, UTC time window, redacted ErrorLink identifiers, Sentry project/group ID, affected Jira issue keys, and sync-log outcome. Do not send secrets, raw payloads, unredacted stack traces, or authorization-bearing HAR files.

Export, purge, and disconnect

Jira administrators can export app-owned installation data without credentials. Before permanent purge, disable Sentry webhook delivery, disconnect Sentry, wait at least 15 minutes for queued work, and type the exact confirmation shown by ErrorLink. Purge does not delete generated Jira issues or source Sentry data. See the privacy policy, security statement, and support policy.