Oz > Integrations
Jira integration
# Jira integration 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. Install the Oz app in Jira The Oz app is not yet published to the Atlassian marketplace. Install the Oz app into your Jira Cloud site using the link provided by your Warp contact. Only Jira site admins can install apps. #### 2. Connect your Jira site to Warp After installing the app, open the app's **Configure** screen inside Jira. This takes you to a Warp page to connect your app installation to your Warp workspace. Once connected, the integration is active for all members of your Warp team. #### 3. (Optional) Configure the default environment, model, and harness In the [Oz web app](https://oz.warp.dev/integrations), open your Jira integration to set the default [environment](/platform/environments/), model, and harness Oz uses for Jira-triggered runs. If you don't set these, Oz uses your team'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. --- ### 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). :::tip When a Jira-triggered run can't start, Oz posts an error comment on the issue. Common codes: * [`feature_not_available`](/reference/api-and-sdk/troubleshooting/errors/feature-not-available/) - your plan doesn't support integrations. * [`integration_disabled`](/reference/api-and-sdk/troubleshooting/errors/integration-disabled/) - the integration was removed or disabled. ::: 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.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
Section titled “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. 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 for details.
- Infrastructure - By default, agents run on Warp-hosted infrastructure. Enterprise teams can self-host agents on their own infrastructure.
- Jira site admin - Installing the Oz app in Jira requires site admin permissions.
1. Install the Oz app in Jira
Section titled “1. Install the Oz app in Jira”The Oz app is not yet published to the Atlassian marketplace. Install the Oz app into your Jira Cloud site using the link provided by your Warp contact. Only Jira site admins can install apps.
2. Connect your Jira site to Warp
Section titled “2. Connect your Jira site to Warp”After installing the app, open the app's Configure screen inside Jira. This takes you to a Warp page to connect your app installation to your Warp workspace.
Once connected, the integration is active for all members of your Warp team.
3. (Optional) Configure the default environment, model, and harness
Section titled “3. (Optional) Configure the default environment, model, and harness”In the Oz web app, open your Jira integration to set the default environment, model, and harness Oz uses for Jira-triggered runs. If you don't set these, Oz uses your team's default configuration.
How to start a run
Section titled “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 in the Warp app, where Jira-triggered runs appear in the All tab.
Troubleshooting
Section titled “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).
For other issues, reach out to your Warp contact or join the Warp community on Slack.
Related pages
Section titled “Related pages”- Integrations overview - How environments and integrations work together.
- Slack and Linear - Other chat- and issue-triggered integrations.
- Managing cloud agents - Monitor Jira-triggered runs across your team.
- Environments - Configure where agents run.