Repository navigation
Conversation
The Jira integration guide said every built-in agent's pre/post scripts expect a GitHub issue number and that Jira-dispatched runs fail, citing #2264. That is out of date. In fullsend-ai/agents, the triage and code harnesses both select a Jira overlay when event.source.system is jira: triage writes its comment, labels, components and close transitions back to the Jira issue, and code reads the issue with a read-only credential and opens a GitHub pull request named after the Jira key (#2265, closed). Prioritize still has no Jira overlay (#2266). Describe each agent's behaviour, note that the default code harness has no trigger, and replace the stale troubleshooting row. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Bill Murdock <bmurdock@redhat.com>
|
🤖 Finished Review · ✅ Success · Started 12:34 PM UTC · Completed 12:44 PM UTC Commit: Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.64 |
Site previewPreview: https://901e071d-site.fullsend-ai.workers.dev Commit: |
|
<!-- fullsend:risk-assessment --> DetailsWhile this is a single-file documentation update with low metadata risk, high recent regression history and multi-author churn on the Jira integration guide elevate the composite risk to moderate. |
ReviewFindingsLow
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Closing: #8943 (merged today for #8920) now documents which built-in agents write what to the Jira issue, and makes the claim here that code posts nothing back to Jira out of date (agents#1843). The remaining docs fixes, the stale trigger text in the guide and the note that prioritize has no Jira support yet (#2266), move to #6672, which I have taken. Written by Bill Murdock with assistance from Claude Code. |
Summary
The Jira integration guide says every built-in agent's pre/post scripts expect a GitHub issue number, so Jira-dispatched runs fail, and that all substantive output goes to GitHub (citing #2264). That is out of date for triage and code. This PR says what each built-in agent does with a Jira work item today.
Draft: I'm about to test the Jira poller with the code agent on a real repo, and I expect to add whatever else that turns up before asking for review.
Related Issue
Related to #2264, #2265, #2266, #6672
Changes
All in
docs/guides/user/jira-integration.md:harness/triage.yamlJira overlay,scripts/lib/jira-triage-ops.lib.shin fullsend-ai/agents).agent/<KEY>-<slug>, with the key in the title and a link to the Jira issue in the body; it posts no Jira comment (harness/code.yamlJira overlay,scripts/pre-code-jira.sh,scripts/post-code.src.sh; Add JIRA support to the code agent #2265 is closed).harness/prioritize.yaml; Add JIRA support to the prioritize agent #2266).trigger, so a repo must add one for/fs-codeorready-to-codeon Jira to dispatch it.#2264 is still open. I haven't touched it here, but the triage Jira overlay looks like it covers what the issue asks for.
#8678 also edits the lines around the Event semantics section, so whichever PR lands second will need a small rebase.
Testing
lychee --offline --include-fragmentson the guide: 0 errorsmake lint(not run; docs-only change)Checklist
🤖 Generated with Claude Code