docs(factories): document Jira integration - #528
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dda424e to
59899c3
Compare
59899c3 to
a2eb24f
Compare
|
/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 |
![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 replaces the placeholder Jira factories page with focused guidance for connecting Jira Cloud to a factory, configuring agent_session_created automations, understanding Rovo session continuity, permissions, delivery caveats, and troubleshooting. I reviewed the attached diff against the docs style guidance, link/comment/test expectations, the supplemental security checklist, and the provided spec context.
Concerns
- No blocking concerns found.
- No approved or repository spec context was provided for this PR, so there is no material spec drift to report.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
|
/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 replaces the Jira factory placeholder with a factory-specific guide for Rovo agent-session intake, filters, permissions, outputs, and troubleshooting. The page is generally scoped to factory behavior and no approved spec context was available for implementation drift review.
Concerns
- The setup step sends readers to the general Jira integration page, which continues into the label-triggered Jira run flow. Without anchoring or caveating the setup-only portion, factory readers can follow the wrong trigger path after connecting the app.
Verdict
Found: 0 critical, 1 important, 0 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
|
|
||
| ## Connect Jira and configure agent sessions | ||
|
|
||
| 1. Follow the [Jira integration setup](../../platform/integrations/jira) to install the app, open its **Configure** page, and click **Connect to Warp**. The Jira installation becomes available to factories in that Warp workspace. |
There was a problem hiding this comment.
| 1. Follow the [Jira integration setup](../../platform/integrations/jira) to install the app, open its **Configure** page, and click **Connect to Warp**. The Jira installation becomes available to factories in that Warp workspace. | |
| 1. Follow the [Jira integration setup](../../platform/integrations/jira#setup) through connecting Jira to your Warp workspace, then return to this page instead of following the label-triggered run steps. The Jira installation becomes available to factories in that Warp workspace. |
a2eb24f to
e58f2e6
Compare
|
/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 replaces the placeholder Jira factory integration page with setup, trigger, filter, permissions, delivery-caveat, and troubleshooting guidance. I reviewed the attached diff, PR description, and spec context; no approved spec context was available, and I found no security-specific issues in the changed content.
Concerns
- The setup section only documents the definitions-as-code path even though the PR scope says the page covers both editor and definitions-as-code trigger paths. Add the editor setup path or narrow the documented scope before merge.
Verdict
Found: 0 critical, 1 important, 0 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
| ## Connect Jira and configure agent sessions | ||
|
|
||
| 1. Follow the [Jira integration setup](https://docs.warp.dev/platform/integrations/jira/#setup) through connecting Jira to your Warp workspace, then return to this page instead of following the label-triggered run steps. The Jira installation becomes available to factories in that Warp workspace. | ||
| 2. Use [factory definitions as code](../factory-as-code) to declare Jira for the factory and add an `agent_session_created` trigger in `automations/<name>/automation.md`. The `agent` field selects the factory agent that handles matching Jira assignments. |
There was a problem hiding this comment.
e58f2e6 to
ac3061f
Compare
|
/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 replaces the placeholder Jira factory integration page with setup prerequisites, definitions-as-code trigger configuration, Rovo session behavior, permissions, delivery caveats, and troubleshooting. I found no approved spec context to compare against and no security-specific findings in the doc-only diff.
Concerns
- The first paragraph uses Rovo before defining it; adding a short definition makes the page more self-contained for readers who land here from search.
Verdict
Found: 0 critical, 0 important, 1 suggestions
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
| --- | ||
|
|
||
| Jira integration documentation for Warp Factories will land in a follow-up PR. | ||
| Connect Jira Cloud to a factory so people can assign Jira work items to **Warp** through Rovo. Jira starts an agent session, a factory automation routes the assignment to its configured agent, and Jira displays the task status and result in the same Rovo session. |
There was a problem hiding this comment.
💡 [SUGGESTION] Define Rovo on first mention so users who arrive from search understand which Jira surface starts the session.
| Connect Jira Cloud to a factory so people can assign Jira work items to **Warp** through Rovo. Jira starts an agent session, a factory automation routes the assignment to its configured agent, and Jira displays the task status and result in the same Rovo session. | |
| Connect Jira Cloud to a factory so people can assign Jira work items to **Warp** through Atlassian Rovo, which starts the agent session from Jira. A factory automation routes the assignment to its configured agent, and Jira displays the task status and result in the same Rovo session. |
|
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 replaces the Jira factory integration placeholder with a focused page for connecting Jira Cloud to factories, configuring the agent_session_created trigger, understanding filters and session continuity, and handling permissions and troubleshooting. The attached spec context contains no approved spec to compare against, and the docs repo does not include a local security-review-pr companion; the security-sensitive authorization and filter caveats are covered clearly in the page.
Concerns
- No blocking concerns found in the attached diff.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
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: Warp Agent <agent@warp.dev> Co-Authored-By: Warp <agent@warp.dev>
ac3061f to
1c394f2
Compare
|
/oz-review |
|
You've used all 5 |
Editorial pass for external readers: - Lead with the user flow in plain language instead of internal routing vocabulary - Restructure setup into three clean steps with the automation example nested under its step, and explain the example inline - Consolidate trigger/filter behavior into one section, removing repeated explanations of when the event fires and keyword case-insensitivity - Replace internal jargon (seeds, intake, factory admission, issue mutations) with plain wording - Surface the filters-vs-access caveat as a caution callout and group permissions/reliability notes into a scannable list - Align title and headers with the sibling Linear page; use root-relative link for the platform setup page Co-Authored-By: Warp <agent@warp.dev>
|
Pushed an editorial pass (c7340ea) tightening this page for external readers:
No factual changes intended — all verified behaviors (event name, filter fields, status states, session continuity, dedup, authorization boundaries) are preserved. Validated with |
Reduce Rovo mentions from six to one. The remaining mention is a recognition pointer in prerequisites (Jira lists the Warp agent among Atlassian's Rovo agents); everywhere else the actors are Warp and the factory agent, and sessions are just agent sessions. Co-Authored-By: Warp <agent@warp.dev>
1 participant
Summary
Adds factory-specific Jira documentation covering app installation and workspace connection, editor and definitions-as-code trigger paths, issue continuity, routing filters, writeback, duplicate-safe repeated delivery, permissions, and troubleshooting.
Final size: 769 prose words. Generic provider installation details remain in the existing platform integration page; this PR focuses only on factory-specific behavior.
Foundation
Shared navigation, route placeholders, Early Access badge support, and guide migrations are merged in #537. This PR now contains only its feature-owned files and passes CI independently.
Validation
npm run typecheck: 0 errorsnpm run build: 377 pages builtLatest source refresh
Rewrites Jira around the working Rovo agent-session model and documents only the emitted agent_session_created event.
Verified against Warp
e72fd7aacand warp-server9be39e484b. Broken, placeholder, partial, and spec-only surfaces remain excluded.Proposed reviewers
Based on the Warp Factories Soft Launch (August 18th) tracker. For planning only; no review requests have been sent.
@jasonkeung@liliwilson@captainsafiaScreenshots
Not included. The page uses a compact trigger/context/output table and links to the existing provider setup page; no approved factory-specific UI assets exist yet.
Unverified claims
None — UI labels, event classes, filters, authorization boundaries, continuity, and writeback behavior were verified against source.
Conversation: https://staging.warp.dev/conversation/5ff89820-2d80-4518-981e-178845029de1
Plans: https://staging.warp.dev/drive/notebook/7ZPKWz7hM5I59o4Gg2ptYi and https://staging.warp.dev/drive/notebook/DpRWhMQ0DLCajPPMggXw5e
Co-Authored-By: Warp Agent agent@warp.dev