docs: clarify user requirements for built-in Jira tools - #820
warp-agent-staging[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This PR was generated with Warp. Comment   |
warp-agent-staging
Bot
added
factory:wilson
warpy-factory
|
@warp-agent-staging[bot] 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 |
![warp-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 a caution to the Jira factory integration docs explaining when built-in Jira tools can use a user-linked Atlassian account and when managed Atlassian MCP is the right fallback. I found no approved spec context to validate against, and the docs-only change did not introduce security-sensitive behavior.
Concerns
- The new callout uses a full
docs.warp.devURL for an internal docs link; the docs style guide and surrounding page use root-relative links within this Starlight space.
Verdict
Found: 0 critical, 0 important, 1 suggestions
Approve with nits
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| * **Jira access doesn't include code access** - Connecting Jira lets agents read and update Jira work items, nothing more. Repository access comes from the factory itself. | ||
|
|
||
| :::caution | ||
| Warp's built-in Jira tools read Jira as the person who created the run; that person must link their Atlassian account to Warp in Jira under **profile** > **Personal settings** > **Warp**. For Jira-triggered runs, the tools act as the Jira user who triggered the run. Runs without a person behind them, such as scheduled runs or runs created by a service account or API key, cannot use these tools. For those runs, add the Atlassian MCP server as a [managed MCP install](https://docs.warp.dev/platform/mcp) instead; it uses the access of the account it was connected with. |
There was a problem hiding this comment.
💡 [SUGGESTION] Use a root-relative internal docs link here to match the docs style guide and the surrounding page's links.
| Warp's built-in Jira tools read Jira as the person who created the run; that person must link their Atlassian account to Warp in Jira under **profile** > **Personal settings** > **Warp**. For Jira-triggered runs, the tools act as the Jira user who triggered the run. Runs without a person behind them, such as scheduled runs or runs created by a service account or API key, cannot use these tools. For those runs, add the Atlassian MCP server as a [managed MCP install](https://docs.warp.dev/platform/mcp) instead; it uses the access of the account it was connected with. | |
| Warp's built-in Jira tools read Jira as the person who created the run; that person must link their Atlassian account to Warp in Jira under **profile** > **Personal settings** > **Warp**. For Jira-triggered runs, the tools act as the Jira user who triggered the run. Runs without a person behind them, such as scheduled runs or runs created by a service account or API key, cannot use these tools. For those runs, add the Atlassian MCP server as a [managed MCP install](/platform/mcp/) instead; it uses the access of the account it was connected with. |
Summary
Add a short caution under Jira Permissions so readers know when built-in Jira tools work and when to use a managed Atlassian MCP install. Only
src/content/docs/factories/integrations/jira.mdxchanges.Related issues
None; requested documentation clarification.
Validation
npm ci,npm run typecheck(0 errors, 0 warnings), andnpm run buildpassed.python3 .agents/skills/style_lint/style_lint.py --changedpassed; five glossary warnings are in unchanged text.git diff --checkpassed. Trunk lint/format skipped because Trunk is not installed; no test suite for this copy-only edit.Screenshots
Computer-use screenshots
View rendered Jira callout — complete caution under Permissions.
Compiled HTML preview — download and open the actual build export, with embedded styles and fonts.
Private artifact links require authorized Warp access. The managed artifact tool omitted its screenshot block; the stored capture was recovered from run metadata.
Follow-ups
None; other pages and product behavior remain unchanged.
Content design plan
Documentation risk
Risk: engineering-review-required
Rationale: Clarifies Jira availability, permission scope, and an account-linking path supplied by the requester.
Source files consulted: src/content/docs/platform/integrations/jira.mdx@3d54389a21bcfbcc9f6211dd0a3f4545b435c122, src/content/docs/platform/mcp.mdx@3d54389a21bcfbcc9f6211dd0a3f4545b435c122
Requested engineering reviewers: none; assignment deferred to factory handoff
Engineering review status: pending
Docs override: none
Unverified claims
No VERIFY markers. Jira access behavior comes from the requester brief; engineering review is pending.