From 8482a77689e6f689df04c0db2ba326969d165ac1 Mon Sep 17 00:00:00 2001 From: jasonkeung Date: Wed, 1 Jul 2026 17:03:25 -0400 Subject: [PATCH 01/10] Add initial Jira integration docs Co-Authored-By: Oz --- .../docs/platform/integrations/index.mdx | 1 + .../docs/platform/integrations/jira.mdx | 59 +++++++++++++++++++ src/sidebar.ts | 1 + 3 files changed, 61 insertions(+) create mode 100644 src/content/docs/platform/integrations/jira.mdx diff --git a/src/content/docs/platform/integrations/index.mdx b/src/content/docs/platform/integrations/index.mdx index 2be2245d8..7e9a32b23 100644 --- a/src/content/docs/platform/integrations/index.mdx +++ b/src/content/docs/platform/integrations/index.mdx @@ -32,6 +32,7 @@ Use the setup walkthrough below for a quick look at how environments connect to * [Integrations quickstart](/platform/integrations/quickstart/) - Trigger your first agent from Slack and watch the run from start to finish. * [Integration setup](/reference/cli/integration-setup/) - Configure environments, GitHub authorization, CLI flags, and integrations in more detail. * [Slack](/platform/integrations/slack/) and [Linear](/platform/integrations/linear/) - Trigger agents from team conversations, issues, and comments. +* [Jira](/platform/integrations/jira/) - Trigger agents from Jira Cloud issues by adding the oz-agent label. * [GitHub Actions](/platform/integrations/github-actions/) - Run agents from CI workflows and repository events. * [GitLab](/platform/integrations/gitlab/), [Bitbucket](/platform/integrations/bitbucket/), and [Azure DevOps](/platform/integrations/azure-devops/) - Connect non-GitHub repositories with tokens and Warp-managed secrets. * [AWS, GCP, and other cloud providers](/platform/integrations/cloud-providers/) - Give cloud agents short-lived access to cloud services. diff --git a/src/content/docs/platform/integrations/jira.mdx b/src/content/docs/platform/integrations/jira.mdx new file mode 100644 index 000000000..bf7baa35e --- /dev/null +++ b/src/content/docs/platform/integrations/jira.mdx @@ -0,0 +1,59 @@ +--- +title: Jira integration +sidebar: + label: "Jira" +description: >- + Trigger Oz agents directly from Jira issues using the oz-agent label. +--- + +The Jira integration lets your team kick off Oz 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 Warp app in Jira + +Install the Warp Forge app into your Jira Cloud site using the link provided by your Warp team admin. 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 where you select which Warp workspace to connect. If you're on a single workspace, the connection happens automatically. + +Once connected, the integration is active for all members of your Warp team. + +#### 3. (Optional) Configure the default environment, model, and harness + +In Warp's agent 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 Build plan or above** — The integration requires a plan that includes cloud agents. +- **Jira site admin** — Installing the Warp app in Jira requires site admin permissions. + +--- + +### Troubleshooting + +If Oz doesn't respond after adding the label, check that: + +- The Warp app is installed and the workspace is connected (see the app's Configure screen in Jira). +- Your team's `JiraEnabled` flag is on — contact your Warp team admin if you're not sure. +- 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. diff --git a/src/sidebar.ts b/src/sidebar.ts index 0f6862ff4..5661ea3ec 100644 --- a/src/sidebar.ts +++ b/src/sidebar.ts @@ -363,6 +363,7 @@ export const sidebarTopics: StarlightSidebarTopicsUserConfig = [ { slug: 'platform/integrations/quickstart', label: 'Quickstart' }, 'platform/integrations/slack', 'platform/integrations/linear', + 'platform/integrations/jira', { label: 'GitHub Actions', collapsed: true, From 6f724ad38d192897f62762959db773542eea9b9b Mon Sep 17 00:00:00 2001 From: Jason Keung Date: Wed, 1 Jul 2026 17:05:08 -0400 Subject: [PATCH 02/10] Apply suggestion from @jasonkeung --- src/content/docs/platform/integrations/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/platform/integrations/index.mdx b/src/content/docs/platform/integrations/index.mdx index 7e9a32b23..c7d99fc61 100644 --- a/src/content/docs/platform/integrations/index.mdx +++ b/src/content/docs/platform/integrations/index.mdx @@ -32,7 +32,7 @@ Use the setup walkthrough below for a quick look at how environments connect to * [Integrations quickstart](/platform/integrations/quickstart/) - Trigger your first agent from Slack and watch the run from start to finish. * [Integration setup](/reference/cli/integration-setup/) - Configure environments, GitHub authorization, CLI flags, and integrations in more detail. * [Slack](/platform/integrations/slack/) and [Linear](/platform/integrations/linear/) - Trigger agents from team conversations, issues, and comments. -* [Jira](/platform/integrations/jira/) - Trigger agents from Jira Cloud issues by adding the oz-agent label. +* [Jira](/platform/integrations/jira/) - Trigger agents from Jira Cloud issues. * [GitHub Actions](/platform/integrations/github-actions/) - Run agents from CI workflows and repository events. * [GitLab](/platform/integrations/gitlab/), [Bitbucket](/platform/integrations/bitbucket/), and [Azure DevOps](/platform/integrations/azure-devops/) - Connect non-GitHub repositories with tokens and Warp-managed secrets. * [AWS, GCP, and other cloud providers](/platform/integrations/cloud-providers/) - Give cloud agents short-lived access to cloud services. From c38c27626cf4a83a3cc59ea83b792e1d358c35a7 Mon Sep 17 00:00:00 2001 From: Jason Keung Date: Wed, 1 Jul 2026 18:40:58 -0400 Subject: [PATCH 03/10] Apply suggestion from @oz-for-oss[bot] Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com> --- src/content/docs/platform/integrations/jira.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/platform/integrations/jira.mdx b/src/content/docs/platform/integrations/jira.mdx index bf7baa35e..031c09e6d 100644 --- a/src/content/docs/platform/integrations/jira.mdx +++ b/src/content/docs/platform/integrations/jira.mdx @@ -3,10 +3,10 @@ title: Jira integration sidebar: label: "Jira" description: >- - Trigger Oz agents directly from Jira issues using the oz-agent label. + Trigger cloud agent runs directly from Jira issues using the `oz-agent` label. --- -The Jira integration lets your team kick off Oz 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. +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. From 88fe963f3156b8312485456be0274d7c1d911240 Mon Sep 17 00:00:00 2001 From: Jason Keung Date: Wed, 1 Jul 2026 18:41:56 -0400 Subject: [PATCH 04/10] Apply suggestions from code review Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com> --- src/content/docs/platform/integrations/jira.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/platform/integrations/jira.mdx b/src/content/docs/platform/integrations/jira.mdx index 031c09e6d..91109d4de 100644 --- a/src/content/docs/platform/integrations/jira.mdx +++ b/src/content/docs/platform/integrations/jira.mdx @@ -43,7 +43,7 @@ In Warp's agent settings, you can configure the default environment, model, and ### Requirements - **Jira Cloud** — Jira Server and Data Center are not supported. -- **Warp Build plan or above** — The integration requires a plan that includes cloud agents. +- **Plan and credits** - 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. - **Jira site admin** — Installing the Warp app in Jira requires site admin permissions. --- From 43c3814ca3885e74dabcd6b600b3a3dadc007ae7 Mon Sep 17 00:00:00 2001 From: Jason Keung Date: Wed, 1 Jul 2026 18:44:52 -0400 Subject: [PATCH 05/10] Apply suggestions from code review Co-authored-by: Jason Keung --- src/content/docs/platform/integrations/jira.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/content/docs/platform/integrations/jira.mdx b/src/content/docs/platform/integrations/jira.mdx index 91109d4de..70135f4b6 100644 --- a/src/content/docs/platform/integrations/jira.mdx +++ b/src/content/docs/platform/integrations/jira.mdx @@ -26,7 +26,7 @@ When the run finishes, Oz posts a summary comment to the issue with links to any #### 1. Install the Warp app in Jira -Install the Warp Forge app into your Jira Cloud site using the link provided by your Warp team admin. Only Jira site admins can install apps. +The Oz app is not yet published to the Atlassian marketplace. Install the Warp Forge 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 @@ -53,7 +53,6 @@ In Warp's agent settings, you can configure the default environment, model, and If Oz doesn't respond after adding the label, check that: - The Warp app is installed and the workspace is connected (see the app's Configure screen in Jira). -- Your team's `JiraEnabled` flag is on — contact your Warp team admin if you're not sure. - 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. From fa622b996e1ba0c65db795a8967ea5801dbe6f16 Mon Sep 17 00:00:00 2001 From: Jason Keung Date: Wed, 1 Jul 2026 18:46:37 -0400 Subject: [PATCH 06/10] Apply suggestions from code review Co-authored-by: Jason Keung --- src/content/docs/platform/integrations/jira.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/content/docs/platform/integrations/jira.mdx b/src/content/docs/platform/integrations/jira.mdx index 70135f4b6..0e865dfb8 100644 --- a/src/content/docs/platform/integrations/jira.mdx +++ b/src/content/docs/platform/integrations/jira.mdx @@ -24,9 +24,9 @@ When the run finishes, Oz posts a summary comment to the issue with links to any ### Setup -#### 1. Install the Warp app in Jira +#### 1. Install the Oz app in Jira -The Oz app is not yet published to the Atlassian marketplace. Install the Warp Forge app into your Jira Cloud site using the link provided by your Warp contact. Only Jira site admins can install apps. +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 @@ -36,7 +36,7 @@ Once connected, the integration is active for all members of your Warp team. #### 3. (Optional) Configure the default environment, model, and harness -In Warp's agent 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. +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. --- @@ -44,7 +44,7 @@ In Warp's agent settings, you can configure the default environment, model, and - **Jira Cloud** — Jira Server and Data Center are not supported. - **Plan and credits** - 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. -- **Jira site admin** — Installing the Warp app in Jira requires site admin permissions. +- **Jira site admin** — Installing the Oz app in Jira requires site admin permissions. --- @@ -52,7 +52,7 @@ In Warp's agent settings, you can configure the default environment, model, and If Oz doesn't respond after adding the label, check that: -- The Warp app is installed and the workspace is connected (see the app's Configure screen in Jira). +- 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. From 0c49299bee4565074bcff902a74481b1e842e4da Mon Sep 17 00:00:00 2001 From: Jason Keung Date: Wed, 1 Jul 2026 18:47:21 -0400 Subject: [PATCH 07/10] Update src/content/docs/platform/integrations/jira.mdx --- src/content/docs/platform/integrations/jira.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/platform/integrations/jira.mdx b/src/content/docs/platform/integrations/jira.mdx index 0e865dfb8..b2de5bfc9 100644 --- a/src/content/docs/platform/integrations/jira.mdx +++ b/src/content/docs/platform/integrations/jira.mdx @@ -3,7 +3,7 @@ title: Jira integration sidebar: label: "Jira" description: >- - Trigger cloud agent runs directly from Jira issues using the `oz-agent` label. + 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. From 3203bb5b6de7ca4b3b6c9d4a99e31bd1cff89c08 Mon Sep 17 00:00:00 2001 From: Jason Keung Date: Wed, 1 Jul 2026 18:56:42 -0400 Subject: [PATCH 08/10] Apply suggestions from code review Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com> Co-authored-by: Jason Keung --- src/content/docs/platform/integrations/jira.mdx | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/content/docs/platform/integrations/jira.mdx b/src/content/docs/platform/integrations/jira.mdx index b2de5bfc9..257e7e36f 100644 --- a/src/content/docs/platform/integrations/jira.mdx +++ b/src/content/docs/platform/integrations/jira.mdx @@ -30,7 +30,7 @@ The Oz app is not yet published to the Atlassian marketplace. Install the Oz app #### 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 where you select which Warp workspace to connect. If you're on a single workspace, the connection happens automatically. +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. @@ -42,9 +42,11 @@ In your integration settings, you can configure the default environment, model, ### Requirements -- **Jira Cloud** — Jira Server and Data Center are not supported. -- **Plan and credits** - 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. -- **Jira site admin** — Installing the Oz app in Jira requires site admin permissions. +- **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. --- From 3ee0559a3c6b97768c7d14b37c7f76d7ea4aecd2 Mon Sep 17 00:00:00 2001 From: jasonkeung Date: Wed, 8 Jul 2026 19:12:21 -0400 Subject: [PATCH 09/10] =?UTF-8?q?docs(jira):=20apply=20review=20feedback?= =?UTF-8?q?=20=E2=80=94=20terminology,=20requirements,=20section=20order,?= =?UTF-8?q?=20troubleshooting?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Remove early-access caution block - Add 'using the oz-agent label' to description - Reorder sections: Requirements → Setup → How to start a run → Troubleshooting - Requirements: match Slack/Linear wording exactly (team membership, plan/credits, infrastructure); drop cloud environment, GitHub auth, identity bullets - Step 2: rename to 'Connect your Jira site to Warp' - Step 3: link to oz.warp.dev/integrations (Oz web app) - How to start a run: add Agent Management Panel cross-link - Troubleshooting: switch to * bullets, add error-code tip block, fix community link to Warp Slack - Add Related pages section - index.mdx: add Jira to intro sentence Co-Authored-By: Oz --- .../docs/platform/integrations/index.mdx | 2 +- .../docs/platform/integrations/jira.mdx | 52 ++++++++++++------- 2 files changed, 33 insertions(+), 21 deletions(-) diff --git a/src/content/docs/platform/integrations/index.mdx b/src/content/docs/platform/integrations/index.mdx index c7d99fc61..c67307473 100644 --- a/src/content/docs/platform/integrations/index.mdx +++ b/src/content/docs/platform/integrations/index.mdx @@ -7,7 +7,7 @@ description: >- --- import VideoEmbed from '@components/VideoEmbed.astro'; -Warp integrations let your team trigger agents directly from the terminal, or from tools like [Slack](/platform/integrations/slack/) and [Linear](/platform/integrations/linear/). Once set up, agents can: +Warp integrations let your team trigger agents directly from the terminal, or from tools like [Slack](/platform/integrations/slack/), [Linear](/platform/integrations/linear/), and [Jira](/platform/integrations/jira/). Once set up, agents can: * Read conversation or issue context * Run code inside your codebase in a remote environment diff --git a/src/content/docs/platform/integrations/jira.mdx b/src/content/docs/platform/integrations/jira.mdx index 257e7e36f..524d5e365 100644 --- a/src/content/docs/platform/integrations/jira.mdx +++ b/src/content/docs/platform/integrations/jira.mdx @@ -3,22 +3,20 @@ title: Jira integration sidebar: label: "Jira" description: >- - Trigger cloud agent runs directly from Jira issues. + 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. -:::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. +### Requirements -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. +* **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. --- @@ -28,7 +26,7 @@ When the run finishes, Oz posts a summary comment to the issue with links to any 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 +#### 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. @@ -36,17 +34,15 @@ 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. +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. --- -### Requirements +### How to start a run -- **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. +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. --- @@ -54,7 +50,23 @@ In your integration settings, you can configure the default environment, model, 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). +* 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 -For other issues, reach out to your Warp contact or post in our community. +* [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. From 811c36bd29ee08cdefef8be166fb02febb12770a Mon Sep 17 00:00:00 2001 From: jasonkeung Date: Fri, 10 Jul 2026 12:22:22 -0700 Subject: [PATCH 10/10] chore: make jira.mdx a draft, drop sidebar and index links Co-Authored-By: Oz --- src/content/docs/platform/integrations/index.mdx | 3 +-- src/content/docs/platform/integrations/jira.mdx | 1 + src/sidebar.ts | 1 - 3 files changed, 2 insertions(+), 3 deletions(-) diff --git a/src/content/docs/platform/integrations/index.mdx b/src/content/docs/platform/integrations/index.mdx index c67307473..2be2245d8 100644 --- a/src/content/docs/platform/integrations/index.mdx +++ b/src/content/docs/platform/integrations/index.mdx @@ -7,7 +7,7 @@ description: >- --- import VideoEmbed from '@components/VideoEmbed.astro'; -Warp integrations let your team trigger agents directly from the terminal, or from tools like [Slack](/platform/integrations/slack/), [Linear](/platform/integrations/linear/), and [Jira](/platform/integrations/jira/). Once set up, agents can: +Warp integrations let your team trigger agents directly from the terminal, or from tools like [Slack](/platform/integrations/slack/) and [Linear](/platform/integrations/linear/). Once set up, agents can: * Read conversation or issue context * Run code inside your codebase in a remote environment @@ -32,7 +32,6 @@ Use the setup walkthrough below for a quick look at how environments connect to * [Integrations quickstart](/platform/integrations/quickstart/) - Trigger your first agent from Slack and watch the run from start to finish. * [Integration setup](/reference/cli/integration-setup/) - Configure environments, GitHub authorization, CLI flags, and integrations in more detail. * [Slack](/platform/integrations/slack/) and [Linear](/platform/integrations/linear/) - Trigger agents from team conversations, issues, and comments. -* [Jira](/platform/integrations/jira/) - Trigger agents from Jira Cloud issues. * [GitHub Actions](/platform/integrations/github-actions/) - Run agents from CI workflows and repository events. * [GitLab](/platform/integrations/gitlab/), [Bitbucket](/platform/integrations/bitbucket/), and [Azure DevOps](/platform/integrations/azure-devops/) - Connect non-GitHub repositories with tokens and Warp-managed secrets. * [AWS, GCP, and other cloud providers](/platform/integrations/cloud-providers/) - Give cloud agents short-lived access to cloud services. diff --git a/src/content/docs/platform/integrations/jira.mdx b/src/content/docs/platform/integrations/jira.mdx index 524d5e365..87ed7f395 100644 --- a/src/content/docs/platform/integrations/jira.mdx +++ b/src/content/docs/platform/integrations/jira.mdx @@ -1,5 +1,6 @@ --- title: Jira integration +draft: true sidebar: label: "Jira" description: >- diff --git a/src/sidebar.ts b/src/sidebar.ts index cebc9c7fe..3adb29616 100644 --- a/src/sidebar.ts +++ b/src/sidebar.ts @@ -363,7 +363,6 @@ export const sidebarTopics: StarlightSidebarTopicsUserConfig = [ { slug: 'platform/integrations/quickstart', label: 'Quickstart' }, 'platform/integrations/slack', 'platform/integrations/linear', - 'platform/integrations/jira', { label: 'GitHub Actions', collapsed: true,