What authentication scope does Verabase require?

Verabase requires standard read permissions on issues, projects, and users to build grounding context. Admin credentials are only used to configure webhook endpoints in Jira.

Connect Jira with Verabase

Q: Is Jira Server (on-premise) supported?

Verabase natively connects to Jira Cloud (API tokens can be generated at id.atlassian.com ). For Jira Server or Data Center deployments behind a firewall, connection requires the Verabase VPN gateway or the Webhook Gateway.

Connect Jira Software to Verabase to sync issues, project tasks, and sprint statuses so your AI agents can help resolve bugs and track features.

What syncs

Jira Issues (Bugs, Tasks)Sprint & release versionsAssignees & user profilesComments & attachmentsCustom issue fields

Automation triggers

Issue created

When a new bug or task is filed in Jira, Verabase updates the development agent's knowledge mapping.

Status transitioned

When a ticket moves (e.g. In Progress to In QA), Verabase updates order information and triggers follow-up context updates.

Comment added

When engineering posts comments detailing root cause analysis, the self-healing knowledge loop updates related FAQ drafts.

Setup guide

Estimated setup time: ~8 minutes. Prerequisites: Jira Cloud administrator access. Personal or Organization Atlassian API token.

Create Atlassian API token

Log in to your Atlassian dashboard and navigate to id.atlassian.com/manage-profile/security/api-tokens" target="_blank" rel="noopener">Atlassian Profile Security API Tokens. Click Create API token, label it "Verabase Integration", and copy the token string immediately.

Add credentials in Verabase Settings

Navigate to Settings → Integrations → Add Jira in your Verabase dashboard. Enter your site domain (e.g., acme.atlassian.net), admin profile email address, and the generated API token.

Configure sync mapping scope

Choose which Jira Projects and boards should be synchronized. Map your fields using the Jira Issues API endpoint parameters. You can limit sync to specific project keys (e.g., DEV, SUPPORT) to restrict data exposure.

Register real-time Webhooks

Ensure that webhook sync is enabled. Verabase will register a webhook listener at `https://app.verabase.io/webhooks/jira` using standard Jira Webhooks API specifications. Click Test Connection to complete registration.

Data Flow & Security Details

Data Read: Connects via the secure Jira Cloud REST API to query issues, sprints, and boards.
Data Written: Current integration is read-only. Issue tracking metadata is fetched via secure KMS-encrypted tokens and is never stored in plaintext.
Limits: Sync limit is capped at 10,000 active tickets per project directory. Attachement scanning does not support binary files exceeding 25MB.

Frequently asked questions

Does Verabase support write-back to Jira issues?

Currently, the Jira integration is read-only. Verabase reads ticket status and comments to provide context to AI agents but does not create or modify Jira issues. Issue creation via AI is on the product roadmap.

Is Jira Server (on-premise) supported?

Verabase natively connects to Jira Cloud. For Jira Server or Data Center deployments behind a firewall, connection requires the Verabase VPN gateway or the Webhook Gateway.

Can we filter issues by JQL query?

Yes. In the advanced settings of the integration, you can provide a custom JQL (Jira Query Language) string to restrict exactly which tickets Verabase will fetch and index.

Related integrations

Ready to sync with Jira?

Join the waitlist for early access to the self-healing knowledge platform.

Get early access to Jira integration