docs: publish Jira integration page with self-serve setup flow#338
docs: publish Jira integration page with self-serve setup flow#338jasonkeung wants to merge 2 commits into
Conversation
- 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>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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 Powered by Oz |
There was a problem hiding this comment.
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
Co-Authored-By: Oz <oz-agent@warp.dev>
hongyi-chen
left a comment
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
might be worth linking them out to the jira platform somewhere here, just for ease of access
There was a problem hiding this comment.
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. | ||
|
|
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
is there anything an admin needs to do on the jira side? can anyone install warp / oz onto jira, without admin permissions?
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
draft: trueflag so the page publishessrc/sidebar.ts
src/content/docs/platform/integrations/index.mdx
Additional context
warp-server(jira/jira_forge.go,jira/jira_forge_claim.go,forge-jira/,client/src/jira/)npm run buildand the internal link checker passCo-Authored-By: Oz oz-agent@warp.dev