Repository navigation
docs(#6672): document built-in Jira triggers in the Jira guide - #8962
Merged
Merged
Conversation
The default triage harness already matches Jira events, and agents#1842 added a Jira-capable trigger to the default code harness (a /fs-code comment from a human, or the ready-to-code label being added). The Jira integration guide still said built-in agents need a hand-written Jira trigger and pointed at #6672. - Setup overview step 6 and Repo configuration now list which built-in agents match Jira events and from which agents release, keep the advice for earlier pins and custom agents, and note that prioritize has no Jira support yet (#2266). - How it works documents the app account type and display-name bot signals from actorKind, and why the poller needs a dedicated account. - New section on issues created with the trigger label already applied: the first poll emits an opened event, not label_changed, so the code trigger does not fire; comment /fs-code or re-add the label instead. - Slash-command text now says the rest of the line is recorded as transition.comment.instruction, which no Jira-run agent reads, and that triage and code read the issue's comments via jira-ro. Note: pre-commit could not fetch hook repos (TLS error in sandbox). Ran lint-docs-links, lint-broken-symlinks and lychee (lint-md-links) directly; all passed. Whitespace/EOF checks verified manually. The VitePress site build was not run (no node_modules in sandbox). Fixes #6672 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Site previewPreview: https://8d8d7078-site.fullsend-ai.workers.dev Commit: |
|
🤖 Finished Review · ✅ Success · Started 6:10 PM UTC · Completed 6:19 PM UTC Commit: Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.74 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
<!-- fullsend:risk-assessment --> DetailsDocs-only update authored by a bot with no protected path changes, elevated from low to moderate risk by high 30-day churn, multi-author contention, and frequent recent fixes on the modified guide. |
|
Looks good to me |
ggallen
approved these changes
Oct 31, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates
docs/guides/user/jira-integration.mdto match the code now that the built-in triage and code harnesses ship Jira-capable triggers. The default code trigger comes from fullsend-ai/agents#1842 and ships in the agents release that follows v0.52.0. Docs only.Related Issue
#6672. The closing reference is added automatically.
Changes
harness/triage.yaml,harness/code.yaml,harness/prioritize.yaml,harness/review.yaml,harness/fix.yamlandharness/retro.yamlonfullsend-ai/agentsmain.app, and a display name that ends inbot/automationas a separate word or starts withAutomation for. Also added a "Use a dedicated account for the poller" section giving the three reasons from the issue.actorKindandautomationDisplayNamePatternininternal/jirapoll/convert.go, andfilterBotEventsininternal/jirapoll/poller.go.openedevent, with the reporter as actor and the current labels, and only when the issue was created within the 24-hour backfill window.label_changedevents come only from changelog entries, so the code trigger does not fire. The default triage trigger does matchopened. To start the code agent, comment/fs-codeor remove the label and add it again.detectChanges,mapChangelogItemanddiffLabelsininternal/jirapoll/discover.go. Label-added events from Jira still go through the role threshold (authorizeEventininternal/harnessdispatch/auth.go).transition.comment.instruction, and later lines are not part of it. No agent that runs from Jira reads that field. Only fix gets an instruction (HUMAN_INSTRUCTION), and it is parsed from the/fs-fixcomment or note body, not from the normalized event. Triage and code read the Jira issue and its comments through thejira-roprovider.extractCommandininternal/jirapoll/convert.go, the fix "Extract PR number and context" step in.github/workflows/reusable-dispatch.yml, andrun-agent-job.shin the GitLab scaffold.scripts/pre-fix.sh, the Jira overlay inharness/code.yaml(providers/jira-ro.yaml),scripts/pre-code-jira.sh,skills/code-implementation/SKILL.md(Jira issue fetch) andskills/jira-forge/SKILL.md(comment listing).Testing
make lintpasses.pre-commitcould not fetch its hook repositories in the sandbox (TLS certificate error), so I ran these hooks directly on the changed file and they passed:hack/lint-docs-links,hack/lint-broken-symlinksandlychee --offline --include-fragments(lint-md-links). I checked trailing whitespace, end of file and line endings by hand. The VitePress site build was not run.Checklist
!for breaking changes)🤖 Generated with Claude Code
Closes #6672
Post-script verification
agent/6672-jira-builtin-triggers-docs)25811c9a815e2c27d397d41e45c59819b1302f54..HEAD)