Skip to content

docs(#6672): document built-in Jira triggers in the Jira guide - #8962

Merged
ggallen merged 1 commit into
mainfrom
agent/6672-jira-builtin-triggers-docs
Oct 31, 2026
Merged

ggallen merged 1 commit into
mainfrom
agent/6672-jira-builtin-triggers-docs

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

Summary

Updates docs/guides/user/jira-integration.md to 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

  • Built-in triggers (goal 1). Rewrote Setup overview step 6, including its warning box, and the Repo configuration section. A table now lists the Jira events each built-in trigger matches and the agents release it ships in: triage from the release that follows v0.49.0, code from the release that follows v0.52.0. The advice for repos pinned to an earlier release and for custom agents stays. Prioritize is noted as lacking Jira support (Add JIRA support to the prioritize agent #2266), and review, fix and retro as not running from Jira events. The references to jira-poll: built-in harness files lack CEL triggers, causing 0 dispatches #6672 are gone.
    • Checked against harness/triage.yaml, harness/code.yaml, harness/prioritize.yaml, harness/review.yaml, harness/fix.yaml and harness/retro.yaml on fullsend-ai/agents main.
  • Dedicated poller account (goal 2). Added the other bot signals: account type app, and a display name that ends in bot/automation as a separate word or starts with Automation for . Also added a "Use a dedicated account for the poller" section giving the three reasons from the issue.
    • Checked against actorKind and automationDisplayNamePattern in internal/jirapoll/convert.go, and filterBotEvents in internal/jirapoll/poller.go.
  • Label already applied at creation (goal 3). New "Labels present when an issue is created" section. On an issue's first poll the poller emits an opened event, with the reporter as actor and the current labels, and only when the issue was created within the 24-hour backfill window. label_changed events come only from changelog entries, so the code trigger does not fire. The default triage trigger does match opened. To start the code agent, comment /fs-code or remove the label and add it again.
    • Checked against detectChanges, mapChangelogItem and diffLabels in internal/jirapoll/discover.go. Label-added events from Jira still go through the role threshold (authorizeEvent in internal/harnessdispatch/auth.go).
  • Slash-command instructions (goal 4). The rest of the command line is recorded as 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-fix comment or note body, not from the normalized event. Triage and code read the Jira issue and its comments through the jira-ro provider.
    • Checked against extractCommand in internal/jirapoll/convert.go, the fix "Extract PR number and context" step in .github/workflows/reusable-dispatch.yml, and run-agent-job.sh in the GitLab scaffold.
    • In the agents repo: scripts/pre-fix.sh, the Jira overlay in harness/code.yaml (providers/jira-ro.yaml), scripts/pre-code-jira.sh, skills/code-implementation/SKILL.md (Jira issue fetch) and skills/jira-forge/SKILL.md (comment listing).
  • Prerequisites, Actor role resolution and the minimum-permissions text are unchanged, because feat(#8401): authorize Jira poll actors without project admin #8892 rewrites them. The step 6 warning box keeps its final lines, where feat(#8401): authorize Jira poll actors without project admin #8892 appends text, but rewording the lines above them may still cause a small merge conflict.

Testing

  • make lint passes. pre-commit could 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-symlinks and lychee --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.
  • Tests added/updated for new or modified logic. Not applicable: docs only.

Checklist

  • PR title follows Conventional Commits (correct type, ! for breaking changes)
  • Commits are signed off (DCO): not applicable, autonomous agent commit
  • I wrote this contribution myself and can explain all changes in it: written by the fullsend code agent

🤖 Generated with Claude Code


Closes #6672

Post-script verification

  • Branch is not main/master (agent/6672-jira-builtin-triggers-docs)
  • Secret scan passed (gitleaks — 25811c9a815e2c27d397d41e45c59819b1302f54..HEAD)
  • PR body secret scan passed (gitleaks — no-git)
  • Final PR description secret scan passed (gitleaks — no-git)

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>
@github-actions

Copy link
Copy Markdown

Site preview

Preview: https://8d8d7078-site.fullsend-ai.workers.dev

Commit: cfe3ba40e7b717386317ef4743bd053bf4395402

@fullsend-ai-review

fullsend-ai-review Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 6:10 PM UTC · Completed 6:19 PM UTC

Commit: cfe3ba4 · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.74

@fullsend-ai-review fullsend-ai-review Bot added the risk/moderate PR risk: moderate label Oct 30, 2026
@codecov

codecov Bot commented Oct 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@fullsend-ai-review

Copy link
Copy Markdown

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Docs-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.

@fullsend-ai-review

Copy link
Copy Markdown

Looks good to me

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Oct 30, 2026
@ggallen
ggallen added this pull request to the merge queue Oct 31, 2026
Merged via the queue into main with commit e0d15b3 Oct 31, 2026
74 of 75 checks passed
@ggallen
ggallen deleted the agent/6672-jira-builtin-triggers-docs branch October 31, 2026 11:34

This branch was successfully deployed

1 active and 1 inactive deployments
site-preview — cfe3ba40 Deployed Oct 30, 2026 by github-actions[bot]
dev — cfe3ba40 Deployed Oct 30, 2026 by fullsend-ai-coder[bot] via behaviour #18398
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-merge All reviewers approved — ready to merge ready-for-review Triggers review agent dispatch risk/moderate PR risk: moderate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

jira-poll: built-in harness files lack CEL triggers, causing 0 dispatches

2 participants