Repository navigation
docs(#8920): describe Jira triage and code results in Jira guide - #8943
Conversation
The Jira guide still said built-in agents had not been adapted to Jira-sourced runs, that substantive output went to GitHub, and that dispatched runs would fail until #2264 landed. #2264 shipped the work-item identity, and fullsend-ai/agents#1843 made triage and code write their results to the originating Jira issue. Replace the stale passages in the event-semantics section, the repo configuration paragraph, and the Troubleshooting table with a "Where built-in agent results appear" subsection. It states which results go to Jira (triage comment, labels, components, configured transitions, and the code-stage update with the PR/MR link) and which artifacts stay on the GitHub or GitLab code host. It also covers retry idempotency, visible write failures, bot-loop protection, and runner-only Jira credentials. Each claim was checked against agents#1843 and the agents triage and code harnesses. pre-commit could not fetch hook repositories (TLS verification error), so the applicable hooks were run directly: pre-commit-hooks checks, gitleaks via scan-secrets, lint-docs-links, lint-broken-symlinks, and lychee. Closes #8920 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
🤖 Finished Review · ✅ Success · Started 12:43 PM UTC · Completed 12:55 PM UTC Commit: Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.97 |
Site previewPreview: https://da1561df-site.fullsend-ai.workers.dev Commit: |
|
<!-- fullsend:risk-assessment --> DetailsDocumentation update across three files by a bot with matching issue scope, with moderate risk driven by high recent churn and coupling on the active Jira integration guide. Previous run<!-- fullsend:risk-assessment --> DetailsSingle-file documentation update by a bot with matching issue scope, with moderate risk driven by high recent churn and coupling on the active Jira integration guide. |
|
Looks good to me Earlier findings
Labels: PR changes user-facing documentation Previous run<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W3sic2V2ZXJpdHkiOiJsb3ciLCJjYXRlZ29yeSI6ImFwaS1jb250cmFjdCIsImZpbGUiOiJkb2NzL2d1aWRlcy91c2VyL2ppcmEtaW50ZWdyYXRpb24ubWQiLCJpZCI6ImZfZjg0MDYyNzc2NmY0MjJmOSIsImxpbmUiOjExMSwiYWN0aW9uYWJsZSI6dHJ1ZX0seyJzZXZlcml0eSI6ImxvdyIsImNhdGVnb3J5IjoiZG9jLXN0eWxlIiwiZmlsZSI6ImRvY3MvZ3VpZGVzL3VzZXIvamlyYS1pbnRlZ3JhdGlvbi5tZCIsImlkIjoiZl9lNzExNTRiYTY1ZjYwYzU4IiwibGluZSI6MTU3LCJhY3Rpb25hYmxlIjp0cnVlfSx7InNldmVyaXR5IjoibG93IiwiY2F0ZWdvcnkiOiJkb2Mtc3R5bGUiLCJmaWxlIjoiZG9jcy9ndWlkZXMvdXNlci9qaXJhLWludGVncmF0aW9uLm1kIiwiaWQiOiJmXzNkMjUyYzM1YzgzZDRhMmYiLCJsaW5lIjoxNzAsImFjdGlvbmFibGUiOnRydWV9LHsic2V2ZXJpdHkiOiJsb3ciLCJjYXRlZ29yeSI6ImluY29tcGxldGUtZG9jIiwiZmlsZSI6ImRvY3MvZ3VpZGVzL3VzZXIvaXNzdWVzLWNvbW1hbmRzLm1kIiwiaWQiOiJmXzQyODIyY2JjNGQ3OWExNWUiLCJsaW5lIjo5LCJhY3Rpb25hYmxlIjp0cnVlfSx7InNldmVyaXR5IjoibG93IiwiY2F0ZWdvcnkiOiJzdGFsZS1kb2MiLCJmaWxlIjoiZG9jcy9ndWlkZXMvdXNlci9hZG9wdGlvbi5tZCIsImlkIjoiZl80YmE4Mjc5MzUyNTA2YjNkIiwibGluZSI6MTAxLCJhY3Rpb25hYmxlIjp0cnVlfV19 --> ReviewFindingsLow
Next steps:
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
🤖 Finished Fix · ✅ Success · Started 12:57 PM UTC · Completed 1:00 PM UTC Commit: Runtime: claude · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $0.31 |
- jira-integration: attribute the label-creation limit to triage, not Jira - jira-integration: wrap the edited env.runner and Repo configuration paragraphs - issues-commands: mention Jira-sourced triage and code runs - adoption: drop the Jira triage-bridge example now covered by built-in triage Note: pre-commit hooks could not run via pre-commit (hook repos could not be fetched, certificate error). Ran the applicable local hooks directly (lint-docs-links, lychee offline link check); both passed. Addresses #8943 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
🔧 Fix agent — iteration 1 (bot-triggered)Addressed all five low-severity documentation findings. Project CI was passing, so no CI-driven edits were needed. Pre-commit could not fetch hook repositories, so the applicable local docs hooks (link scope and offline link check) were run directly and passed. Fixed (5):
Tests: passed CI inspections (6):
Conflict update: skipped; strategy
|
|
🤖 Finished Review · ✅ Success · Started 1:02 PM UTC · Completed 1:08 PM UTC Commit: Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.25 |
Superseded by updated review
Summary
Updates
docs/guides/user/jira-integration.mdso it matches current behavior. Built-in triage and code agents now write their results to the Jira issue that started the run, and code artifacts stay on the GitHub or GitLab code host. This removes the stale claims that built-in agents "have not been adapted", that output goes to GitHub, and that dispatched runs fail until #2264.Related Issue
#8920. The implementation landed in fullsend-ai/agents#1843. The work-item identity landed in #8922 (#2264).
Changes
JIRA_*_TRANSITION, with issues: add tracker-neutral issue transitions #6704 for tracker-neutral transitions)JIRA_TOKEN/JIRA_USER_EMAILunderenv.runnerin their Jira overlays.I checked each claim against agents#1843 (
docs/code.md,docs/triage.md,harness/code.yaml, and the post-script diffs) and against the agentsharness/triage.yamlJira overlay. The "release that follows v0.52.0" wording is there because #1843 merged after v0.52.0, which is the latest agents release.Testing
pre-commitcould not fetch hook repos in the sandbox (TLS verification error). These were pre-commit-hooks v6.0.0 checks (end-of-file, trailing whitespace, private key, merge conflict, mixed line ending), gitleaks viascan-secrets,hack/lint-docs-links,hack/lint-broken-symlinks, andlychee --offline --include-fragments(0 errors, including the new anchor).Checklist
🤖 Generated with Claude Code
Closes #8920
Post-script verification
agent/8920-jira-result-docs)0f0a0cbd434c80a2071bef1282ffe94941d22842..HEAD)