Docs / Work tools
Jira
Connect a Jira Cloud site over Atlassian OAuth so the agent can open, comment on and transition issues.
Pangea connects to Jira Cloud through Atlassian OAuth. You authorize once in the browser, and there is no API token or site URL to manage. The agent can then work with issues on your site: file a ticket for an incident, comment on progress, and move it to Done when the fix lands.
Connect
1. Start the authorization
As a team Administrator, open Connectors, find Jira and click Add, then click Authorize Jira. Your browser opens Atlassian's consent screen.
2. Choose one site and approve
Grant access to a single Jira site. Pangea asks for these scopes:
| Scope | Why |
|---|---|
read:jira-work |
Read projects, issues and comments |
write:jira-work |
Create and update issues and comments |
read:jira-user |
Resolve assignees |
offline_access |
Keep the connection alive with a refresh token |
read:jira-user lets Pangea read user profiles on your site. That includes display names, avatars and email addresses where your site makes them visible.
3. Return to Pangea
Atlassian sends you back to the Mac app, and the connection completes by itself.
Tokens are stored encrypted and refreshed automatically. Authorizing the same site again updates the existing connection instead of adding a duplicate.
Only Jira Cloud is supported. Jira Data Center and Jira Server are not. Each connection covers one site. If your grant spans several sites, Pangea stops and asks you to authorize again with a single site selected.
In the Pangea app
Jira has no separate browsing view. Its value shows up inside agents, where the issues an agent files or updates are linked in its history. The connection itself lives in Connectors, where an Administrator can manage its allow-list or remove it.
What the agent can do for you
The agent can discover projects and issue types, create issues, comment, search with JQL, and move issues through your workflow transitions. It works best paired with your infrastructure connectors:
- "Investigate the elevated error rate, and open a Jira ticket with what you find." The agent diagnoses through your cloud and observability connectors, then files the issue with the evidence.
- While it works on a fix, it comments progress on the ticket. When the fix lands, it moves the issue through your workflow to Done.
- "What's assigned to me about the payment service?" It searches with JQL and sums up the results.
Permissions and authorization
Team Administrators connect and remove this connection. They can limit it with a member allow-list. Select the connection for the conversation before you ask the agent to use it. Jira permissions stay the outer limit, whatever the prompt or permission mode.
Each action follows Auto Mode and Full Access. Significant cloud infrastructure work uses plans. A ticket, a repository write or a routine API call does not create a plan by itself. If you want to review changes before they are published, say so in your request.
Good to know
- One connection covers one Jira site. Connect again for each extra site.
- The agent works within your existing workflow transitions. It cannot skip states your workflow does not allow.