Repository navigation
docs: clarify Jira attribution for factory automation runs - #955
warp-agent-staging[bot] wants to merge 1 commit into
Conversation
Replace the human-creator-only restriction with the automation creator fallback from warp-server #20620 and preserve exclusions and revocation guidance. Co-Authored-By: Oz <oz-agent@warp.dev>
|
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:docs-factory
![warp-agent-staging[bot]](https://avatars.githubusercontent.com/in/2196476?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
The attribution update matches the server implementation; no prose revisions are needed. Engineering confirmation of production shipping is still required before merge.
Verdict
Checks: build pass, tests pass, CI green, visual proof n/a
Found: 0 critical, 1 important, 0 suggestions, 0 nits
Responding as Docs Factory (V2): Open session · View in factory
| * **Human-created runs** - The tools use the run creator's account. | ||
| * **Automation runs without a human creator** - For factory automations, including scheduled runs, **Run now**, and other automation-triggered runs, the tools use the automation creator's account. Helper agents use the same account, not the last editor's, trigger creator's, or agent's account. | ||
|
|
||
| That person must link their Atlassian account in Jira under **profile** > **Personal settings** > **Warp**. Reads use their Jira permissions. The Warp app makes writes, such as comments, edits, and transitions, after checking that person's permission for the exact action and target. |
There was a problem hiding this comment.
Keep the existing draft/merge hold until the owning engineer confirms warp-server #20620 is deployed with user-scoped reads and permission-checked writes, and records that evidence in the PR. The merged source and supplied local verification do not establish production availability; no wording change is needed while held.
Responding as Docs Factory (V2): Open session · View in factory
What this feature does
Built-in Jira tools use the automation creator's linked Jira account for factory automation runs without a human creator and their helper agents. Human-created runs keep their existing attribution. Reads use that person's permissions; the Warp app makes permission-checked writes. The implementation in warp-server #20620 is merged; production shipping is not confirmed.
Summary
Replace the outdated human-creator-only caution in
src/content/docs/factories/integrations/jira.mdxwith attribution, account-linking, access-revocation, and service-account exclusion rules. Add the Connect Warp troubleshooting item. The standalone Jira integration and unattended-agent guide were checked and need no change.Merge only after warp-server #20620 merges and ships. Opened as a pre-rollout draft at the requester's explicit direction, not as a claim of production availability.
Content design plan
Verification
Run here with Node 24.11.0 via
npx --yes --package=node@24.11.0 --call '…':npm run typecheck— passed, zero errors/warnings, seven existing hints.npm run test:heading-vars— passed, 5 tests.npm run build— passed; existing route, collection, and bundle-size warnings.npm run test:heading-tocs— passed, 3,391 entries across 401 HTML files.npm run test:homepage-json-ld— passed.python3 .agents/skills/style_lint/style_lint.py --changed— exit 0, four glossary advisories (three existing; one for the source-verified Connect Warp label).python3 .agents/skills/validate_ui_refs/validate_ui_refs.py --changed— passed.python3 .agents/skills/check_for_broken_links/check_links.py --internal-only— passed, 4,496 links.python3 .agents/skills/doc_quality_policy/check_compression_contract.py src/content/docs/factories/integrations/jira.mdx --content-type feature-docandgit diff --check— passed.Source: #20620's spec and merged source head
fdd1138dcbd9411d0ff3376e70eacb3f55c2df3b. The requester and upstream PR report Jason's local verification of Run now, cron, a helper, checked writes, unlink/rebind, delete/disable, service-account creator denial, and spoofed metadata. I did not rerun live Jira tests. Source rollout configuration was checked at7bd0ebfc0c9aa12f48a27cde960fdfa293eaec64; this is not deployment evidence.Unverified claims
Documentation risk
Risk: engineering-review-required
Rationale: Changes Jira permissions and automation attribution claims; production availability awaits confirmation.
Source files consulted: actor.go and resolver.go under warp-server/logic/ai/ambient_agents/managed_mcp/warp_jira_mcp/, plus warp-server/jira/jiracopy/copy.go, at the source head above; warp-server/jira/jiraclient/client.go@7bd0ebfc0c9aa12f48a27cde960fdfa293eaec64.
Requested engineering reviewers: none (ownership resolves only to team warpdotdev/fa-warp-3; docs policy requires a single owning human)
Engineering review status: pending
Docs override: none
Co-Authored-By: Oz oz-agent@warp.dev