> For the complete documentation index, see [llms.txt](/llms.txt). > Markdown versions of each page are available by appending .md to any URL. # Jira integration Trigger cloud agent runs directly from Jira issues using the oz-agent label. The Jira integration lets your team kick off cloud agent runs directly from Jira Cloud issues. When you add the `oz-agent` label to an issue, an agent starts in the cloud and gets to work — then posts status updates and a summary back as Jira comments when it's done. * * * ### Requirements - **Jira Cloud** - Jira Server and Data Center are not supported. - **Team membership** - The Jira integration requires you to be part of a [Warp team](/knowledge-and-collaboration/teams/). Teams can be created on any plan, including Free. - **Plan and credits** - Your team must be on a plan that supports integrations (Build, Max, or Business) and have at least 20 credits available. See [Access, Billing, and Identity](/platform/team-access-billing-and-identity/) for details. - **Infrastructure** - By default, agents run on Warp-hosted infrastructure. Enterprise teams can [self-host agents](/platform/self-hosting/) on their own infrastructure. - **Jira site admin** - Installing the Oz app in Jira requires site admin permissions. * * * ### Setup #### 1\. Open the Jira app installation page In the [Oz web app](https://oz.warp.dev/integrations), find Jira and click **Set up**. On the Atlassian installation page, click **Get app**. #### 2\. Install Oz on your Jira site Choose the Jira Cloud site you want to connect, review the requested permissions, and install Oz. Only Jira site admins can install apps. #### 3\. Open the Oz configuration page In your Jira site, open **Manage apps**. Find Oz, open its three-dot actions menu, then click **Configure**. The configuration page URL for the production app follows this pattern: ``` https://.atlassian.net/jira/settings/apps/configure/40dbc167-16d9-4b68-9752-277c5a52aa01/34808a52-a321-44c2-bac4-a15eb316df50/static/warp-jira-configure/34808a52-a321-44c2-bac4-a15eb316df50 ``` Replace `` with your Jira Cloud site ID. #### 4\. Connect Jira to your Warp workspace On the Oz configuration page in Jira, click **Connect to Warp**. Sign in to Warp if prompted. Warp automatically binds the Jira installation to your Warp workspace. The confirmation page displays **Jira connected** when the connection succeeds. Jira-triggered runs are now available to members of the connected Warp workspace. #### 5\. (Optional) Configure the default environment, model, and harness Return to the [Integrations page in the Oz web app](https://oz.warp.dev/integrations), then click **Edit Jira** to set the default [environment](/platform/environments/), model, harness, and agent for Jira-triggered runs. If you don't change these settings, Oz uses your workspace's default configuration. * * * ### How to start a run Add the label **`oz-agent`** to any Jira issue. Oz will pick it up, post a comment to let you know it's started, and begin working through the task using the issue title, description, and recent comments as context. When the run finishes, Oz posts a summary comment to the issue with links to any pull requests or branches it created, along with a link to the full conversation in Warp. To track runs across your team, open the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app, where Jira-triggered runs appear in the **All** tab. #### Connecting your Jira account to Warp The first time you trigger a run, Oz posts a comment prompting you to connect your Jira account to Warp. Connecting attributes your Jira-triggered runs to your Warp account; the run starts either way. 1. Follow the link in the comment to open the Warp page in your Jira personal settings. The link for the production app follows this pattern: ``` https://.atlassian.net/jira/settings/personal/apps/40dbc167-16d9-4b68-9752-277c5a52aa01/34808a52-a321-44c2-bac4-a15eb316df50 ``` 2. Click **Connect to Warp**. A Warp page opens and links your account automatically. Sign in to Warp first if prompted. The page displays **Jira account connected** when the link succeeds, and the settings page shows a **Connected to Warp** badge. Runs you trigger from then on are attributed to you. * * * ### Troubleshooting If Oz doesn't respond after adding the label, check that: - The Oz app is installed and the workspace is connected (see the app's **Configure** screen in Jira). - The issue is in Jira Cloud (not Server or Data Center). Note When a Jira-triggered run fails to start, Oz updates its comment on the issue to say it could not start the task. Re-add the `oz-agent` label to try again; a new attempt starts a new comment thread. For other issues, reach out to your Warp contact or join the [Warp community on Slack](https://go.warp.dev/join-preview). * * * ### Related pages - [Integrations overview](/platform/integrations/) - How environments and integrations work together. - [Slack](/platform/integrations/slack/) and [Linear](/platform/integrations/linear/) - Other chat- and issue-triggered integrations. - [Managing cloud agents](/platform/managing-cloud-agents/) - Monitor Jira-triggered runs across your team. - [Environments](/platform/environments/) - Configure where agents run.