Jira

{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}

At a glance

  • Availability: Enabled by default.
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider's consent screen.
  • Scopes: read:jira-work, write:jira-work, read:jira-user, offline_access.

Credentials

Set these per environment. See Connect an integration.

These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

VariableRequiredDescription
ATLASSIAN_CLIENT_IDYesAtlassian OAuth 2.0 Client ID (from your app) Docs.
ATLASSIAN_CLIENT_SECRETYesAtlassian OAuth 2.0 Client Secret Docs.
JIRA_CLOUD_IDNoOptional Atlassian site ID; required when the user can access multiple Jira sites Docs.

Setup

  1. Choose who owns the Atlassian OAuth app: On hosted Veryfront, Jira uses the Veryfront-managed Atlassian OAuth app: connect Jira from the project's integrations and approve the Atlassian consent screen, no environment variables needed. Set ATLASSIAN_CLIENT_ID and ATLASSIAN_CLIENT_SECRET only to use your own Atlassian OAuth app, which is required for local and self-hosted runs.
  2. Create an OAuth 2.0 integration: In the Atlassian developer console, create an OAuth 2.0 integration.
  3. Add the Jira API permissions: Under Permissions, add the Jira API and select these scopes: read:jira-work, write:jira-work, read:jira-user. offline_access is requested at authorization time so the connection can refresh its token.
  4. Add the callback URLs: Under Authorization, choose OAuth 2.0 (3LO). Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/jira for hosted Veryfront, or your app origin followed by /api/auth/jira/callback for a local or self-hosted app. Set ATLASSIAN_CLIENT_ID and ATLASSIAN_CLIENT_SECRET from the app's credentials.
  5. Share the app: Under Distribution, set the app to sharing so users outside your own Atlassian account can authorize it.
  6. Verify access: Run List Atlassian Sites (read-only) to find the site's cloud ID, then run List Projects (read-only) against that site. Neither call changes anything.

Provider notes

  • The connection requests read:jira-work, write:jira-work, read:jira-user and offline_access.
  • If the user can reach more than one Atlassian site, set JIRA_CLOUD_ID to the target site's cloud ID from List Atlassian Sites.
  • For project-owned or scheduled automation without browser consent, use a Jira service account instead: /docs/code/guides/integrations/jira
  • Tools that create, update, send or delete data are marked as writes and need write authority; the other tools are read-only.

Provider API reference.

Tools

ToolAccessDescription
List Atlassian Sites<br /><code className="reference-identifier">jira__list_sites</code>ReadList Atlassian sites
List Projects<br /><code className="reference-identifier">jira__list_projects</code>ReadList projects
Get Project<br /><code className="reference-identifier">jira__get_project</code>ReadGet project
Search Issues<br /><code className="reference-identifier">jira__search_issues</code>ReadSearch issues
Get Issue<br /><code className="reference-identifier">jira__get_issue</code>ReadGet issue
Create Issue<br /><code className="reference-identifier">jira__create_issue</code>WriteCreate issue
Update Issue<br /><code className="reference-identifier">jira__update_issue</code>WriteUpdate issue
List Comments<br /><code className="reference-identifier">jira__list_comments</code>ReadList comments
Add Comment<br /><code className="reference-identifier">jira__add_comment</code>WriteAdd comment
Get Transitions<br /><code className="reference-identifier">jira__get_transitions</code>ReadGet transitions
Transition Issue<br /><code className="reference-identifier">jira__transition_issue</code>WriteTransition issue
Search Users<br /><code className="reference-identifier">jira__search_users</code>ReadSearch users

Verify the connection

Call a read tool such as jira__list_sites with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.