Jira

Prerequisites

Create an Atlassian OAuth app and identify the Jira site and projects your users will access. The connected user must have Jira permission for each requested issue operation. Use the Jira REST documentation, OAuth 2.0 guide, and developer console as the source of truth.

Self-hosted setup

1. Create an OAuth 2.0 (3LO) app in the Atlassian developer console.
2. Add https://<your-authlane-host>/api/v1/oauth/jira/callback as its callback URL.
3. Add the Jira API permissions and scopes below, then copy the Client ID and Client Secret.
4. Test with a user who can access the intended cloud site and projects.

Configure authentication

Open Dashboard → Services → Jira → OAuth Configuration, enter the Client ID and Client Secret, save, and enable Jira. Authlane uses PKCE and discovers the connected cloud ID after consent.

Scopes

• read:jira-work reads issues, comments, and available transitions.
• write:jira-work creates, updates, transitions, and comments on issues.
• offline_access lets Authlane refresh the connection without asking the user to reconnect whenever the short-lived access token expires.

Execution path

Prefer Atlassian's official Rovo MCP server at https://mcp.atlassian.com/v1/mcp/authv2 for AI execution; follow the official setup guide. Use the direct Jira adapter only when the server does not expose the required deterministic action or the self-hosted runtime uses an incompatible headless authentication mode.

Available tools

Read issues and workflow

• jira_list_issues
• jira_get_transitions

Create and change issues

• jira_create_issue
• jira_update_issue
• jira_transition_issue
• jira_add_comment

Install @authlane/integration-jira in the SaaS runtime. Each callback obtains a fresh credential lease and calls Jira directly; Authlane never proxies JQL, issue data, or Jira responses.

Connection lifecycle

Atlassian consent creates an encrypted connected connection. Authlane refreshes the credential before expiry only when the provider supplied refresh material. Reconnect after an unrecoverable refresh or expired or error state. A destructive hosted disconnect requires a new connect session with recent reauthentication.

Troubleshooting

• Confirm the connected user can browse the target project before diagnosing an issue-key error.
• jira_transition_issue requires a transition ID currently returned by jira_get_transitions; status names are not transition IDs.
• Invalid JQL fails in Jira itself; test the same query for the connected site and user.