Add initial Jira integration docs#281
Conversation
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 |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR adds an initial Jira integration page and wires it into the integrations landing page and sidebar. The structure is mostly in the right place, and the security pass did not identify code or configuration security findings, but the new page has user-facing terminology and requirements issues that should be fixed before publishing.
Concerns
- The page uses the user-facing phrase "Oz agents" / "Oz agent runs," which the docs terminology guide explicitly says to avoid in favor of "agents" or "cloud agent runs."
- The requirements understate integration access requirements compared with the existing integration docs: they omit credits and the precise eligible plan set.
- Troubleshooting exposes the internal
JiraEnabledflag name and sends users to a Warp team admin, who may not have a way to verify that internal gate.
Verdict
Found: 0 critical, 2 important, 1 suggestions
Request changes
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-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com>
Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com>
Co-authored-by: Jason Keung <jason.keungg@gmail.com>
Co-authored-by: Jason Keung <jason.keungg@gmail.com>
|
/oz-review |
|
I'm re-reviewing this pull request in response to a review 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 adds an initial Jira integration docs page, wires it into the Integrations overview, and adds it to the Platform integrations sidebar. The page covers the early-access flow, but the requirements section omits prerequisites users need before Jira-triggered agents can work on code.
Concerns
- The Jira page should list the required cloud environment and GitHub authorization prerequisites alongside plan, credit, and Jira admin requirements.
- One setup sentence should clarify that the automatic connection behavior applies to a single Warp workspace, not a Jira workspace.
Verdict
Found: 0 critical, 1 important, 1 suggestions
Request changes
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-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com> Co-authored-by: Jason Keung <jason.keungg@gmail.com>
1 participant
Summary
Adds an initial docs page for the Jira integration, which lets teams trigger Oz cloud agents from Jira Cloud issues by adding the
oz-agentlabel.Changes
src/content/docs/platform/integrations/jira.mdx— overview, how to start a run, setup, requirements, and troubleshooting.src/sidebar.ts— adds Jira to the Integrations list (after Linear).src/content/docs/platform/integrations/index.mdx— adds a Jira bullet to the "Get started" list.Note on file location
The original task specified the path
src/content/docs/agent-platform/cloud-agents/integrations/jira.mdx. That path is stale —mainhas been restructured so integrations now live undersrc/content/docs/platform/integrations/(seeslack.mdx,linear.mdx, etc.), and the sidebar referencesplatform/integrations/*slugs. The page was placed there instead so it matches the current structure, appears in the sidebar, and isn't orphaned. Page content is unchanged from the spec.Validation
npm run buildsucceeds (341 pages built), including the new Jira page.Artifacts
Co-Authored-By: Oz oz-agent@warp.dev