Skip to content

docs: publish Jira integration page with self-serve setup flow#338

Open
jasonkeung wants to merge 2 commits into
mainfrom
jason/jira-integration-setup-docs
Open

docs: publish Jira integration page with self-serve setup flow#338
jasonkeung wants to merge 2 commits into
mainfrom
jason/jira-integration-setup-docs

Conversation

@jasonkeung

Copy link
Copy Markdown
Contributor

Summary

Publishes the Jira integration page and rewrites the setup instructions for the current self-serve flow, replacing the old "contact Warp for an install link" guidance.

Changes

src/content/docs/platform/integrations/jira.mdx

  • Removed the draft: true flag so the page publishes
  • Rewrote setup as five steps matching the shipped flow: Set up in the Oz web app → Get app on Atlassian → install on the Jira Cloud site → Manage apps > Oz > ConfigureConnect to Warp (automatic workspace binding)
  • Added URL patterns for the Oz configuration page and the Jira personal settings page, with production app/environment IDs
  • Added a "Connecting your Jira account to Warp" section documenting the account-binding comment and flow for run attribution
  • Replaced the error-code troubleshooting tip (verified inaccurate against warp-server: the Jira notifier no-ops on platform errors) with the actual failed-to-start comment behavior

src/sidebar.ts

  • Added Jira under Integrations after Linear

src/content/docs/platform/integrations/index.mdx

  • Added Jira links alongside Slack and Linear in the intro and Get started list

Additional context

  • Setup and binding flows verified against warp-server (jira/jira_forge.go, jira/jira_forge_claim.go, forge-jira/, client/src/jira/)
  • npm run build and the internal link checker pass

Co-Authored-By: Oz oz-agent@warp.dev

- Remove draft flag from the Jira integration page
- Rewrite setup for the self-serve flow: install from the Oz web app,
  configure via Manage apps in Jira, and connect to a Warp workspace
- Document the account-binding flow for run attribution
- Replace the inaccurate error-code tip with actual failed-to-start behavior
- Add Jira to the Integrations sidebar and overview page

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label Jul 17, 2026
@vercel

vercel Bot commented Jul 17, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jul 17, 2026 6:48pm

Request Review

@oz-for-oss

oz-for-oss Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

@jasonkeung

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@oz-for-oss oz-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR publishes the Jira integration page, updates the setup flow for self-serve installation, and links Jira from the integrations overview and sidebar. I found one clarity issue around the Jira URL placeholder, but no blocking correctness, security, or spec-alignment concerns.

Concerns

  • The Jira URL placeholder uses "site ID" language even though readers need the Atlassian site subdomain.

Verdict

Found: 0 critical, 0 important, 1 suggestion

Approve with nits

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Comment thread src/content/docs/platform/integrations/jira.mdx Outdated
Co-Authored-By: Oz <oz-agent@warp.dev>

@hongyi-chen hongyi-chen left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added a couple of questions that we can expand on, but generally looks good - ty!

#### 2. Install Oz on your Jira site

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.
Choose the Jira Cloud site you want to connect, review the requested permissions, and install Oz. Only Jira site admins can install apps.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

might be worth linking them out to the jira platform somewhere here, just for ease of access

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also, i think worth mentioning a bit about how this affects your jira team - once you install this on jira, does everyone immediately have access to it? does everyone else have to auth into warp / oz?

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.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could be helpful to include a screenshot here!


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

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there anything an admin needs to do on the jira side? can anyone install warp / oz onto jira, without admin permissions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants