---
id: "asgard-ext-jira"
lang: "en"
name: "Jira"
vendor: "Atlassian"
product: "Jira Cloud"
category: "project"
summary: "Lets the Agent look up Jira issues with a shared account, or work as each end user: search, create issues, comment and change status after they confirm."
url: "https://www.asgard-ai.com/extensions/asgard-ext-jira"
docs: "https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/"
source: null
usages: ["build-time","shared-account","personal-account"]
produces: ["Workflow","Toolset","Agent","OAuthProvider","SkillSet"]
requires: {"asgard_cli":">=0.2.0","skills":[],"extensions":[],"platform":["connector"]}
command: "asgard-cli extension get asgard-ext-jira"
handoff: "Use asgard-cli to get the asgard-ext-jira Extension. Help me decide which routes to use. Then start the rollout."
updated: "2026-11-04"
---

# Jira

Lets Asgard Agents look up Jira Cloud issues: which ones are still open, which stage an issue is stuck in and for how long, who is working on it. When each end user connects their own account, the Agent can also create issues, comment, change status and edit fields for them, recorded in their name; the person confirms every change before it is sent.

## Supported uses

| Use | What it does |
|---|---|
| Design time | While the deployment is being designed, the FDE Agent first looks at the projects, issue types, statuses and custom fields on the Jira site, with an account invited to Jira and its API token |
| Shared account | Once live, the Agent looks up the chosen projects with a shared account (e.g. an organization account; a dedicated system account is best): it searches issues and reads one issue with its comments and status history. The token is kept on the platform, out of reach of end users and the AI. Read-only |
| Personal account | Each end user (e.g. members of the organization) clicks Allow once in Sindri with their own Atlassian account, and the Agent searches as that person (it sees only what they can see), creates issues, comments, changes status and edits fields. The person confirms every change before it is sent, and Jira records it in their name |

## What you need

- A Jira Cloud site (`<site>.atlassian.net`). Self-hosted Jira Data Center / Server isn't covered in this version.
- A Jira site admin who invites the account used at design time by email, with browse access to the projects to look at.
- Shared account: a Jira account just for the AI (with a mailbox the organization manages), given only the projects to look up and only browse permission, plus an API token for it (valid for up to a year, so it needs renewing).
- On paid plans, the invited account and the system account each take a Jira user seat. On the Free plan, you can't limit which projects an account can see.
- If the Atlassian organization blocks members from creating API tokens, an organization admin needs to allow it.
- Personal account: someone with the organization's Atlassian account creates an OAuth app in Atlassian's developer console and shares it within the organization. Each end user connects once.

If there's no token or system account yet, the FDE Agent walks you through creating them step by step; no coding needed.