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. :::caution[Early access] The Jira integration is in active development. Functionality may change, and some features are still being built out. We welcome feedback and suggestions. ::: --- ### 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. --- ### 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 workspace 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 your integration settings, you can configure the default environment, model, and harness that Oz will use for runs triggered from Jira. If none is set, Oz uses your team's default configuration. --- ### Requirements - **Jira Cloud** - Jira Server and Data Center are not supported. - **Warp team and eligible plan** - Your team must be on a **Build, Max, or Business** plan with at least **20 credits** available, or on an **Enterprise** plan with a team credit pool. See [Access, Billing, and Identity](/platform/team-access-billing-and-identity/) for details. - **A configured cloud environment** - Agents run inside an [environment](/platform/environments/) that includes the repositories and dependencies they need. Configure a Jira-specific default environment or confirm your team's default configuration includes one. - **GitHub authorization** - Warp needs access to your repositories to clone code and open pull requests. Authorize the Warp GitHub app before using the integration for code tasks. - **Jira site admin** - Installing the Oz app in Jira requires site admin permissions. --- ### 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 post in our community.Trigger cloud agent runs directly from Jira issues.
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.
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.
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 workspace to Warp
Section titled “2. Connect your Jira workspace 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 your integration settings, you can configure the default environment, model, and harness that Oz will use for runs triggered from Jira. If none is set, Oz uses your team's default configuration.
Requirements
Section titled “Requirements”- Jira Cloud - Jira Server and Data Center are not supported.
- Warp team and eligible plan - Your team must be on a Build, Max, or Business plan with at least 20 credits available, or on an Enterprise plan with a team credit pool. See Access, Billing, and Identity for details.
- A configured cloud environment - Agents run inside an environment that includes the repositories and dependencies they need. Configure a Jira-specific default environment or confirm your team's default configuration includes one.
- GitHub authorization - Warp needs access to your repositories to clone code and open pull requests. Authorize the Warp GitHub app before using the integration for code tasks.
- Jira site admin - Installing the Oz app in Jira requires site admin permissions.
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 post in our community.