docs(#6094): add multi-repo polling section to Jira guide - #6103
Conversation
Add a "Multi-repo polling" section to the Jira integration guide
answering deployment questions identified during ROSAENG onboarding:
- Whether each repo needs its own poll workflow (yes — the
--target-repo flag controls entity property namespace and the
GHA concurrency group provides natural isolation)
- How entity property locks namespace across repos via the
{owner}.{repo} key prefix, with a concrete two-repo example
- How the 50-candidate cap interacts with N pollers (per-poller,
not global) and operational considerations for large deployments
(JQL scoping, cron staggering, rate limit monitoring)
Closes #6094
|
🤖 Finished Review · ✅ Success · Started 2:36 PM UTC · Completed 2:48 PM UTC Commit: |
Site previewPreview: https://6e0d11ae-site.fullsend-ai.workers.dev Commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
ReviewFindingsLow
Previous runLooks good to me Labels: PR adds documentation to docs/guides/user/, modifying only a user guide |
![fullsend-ai-review[bot]](https://avatars.githubusercontent.com/in/3478501?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
fullsend-ai-review
Bot
added
ready-for-merge
|
/fs-fix address the one finding above |
|
🤖 Finished Fix · ✅ Success · Started 5:26 PM UTC · Completed 5:32 PM UTC Commit: |
…ling Moves the advice about using Jira Components or labels to segment projects per repo from a buried bullet point into the section introduction, making it a clear best practice recommendation. Addresses review feedback on #6103
🔧 Fix agent — iteration 1 (human-triggered)Addressed 1 review finding: promoted JQL scoping advice (using Jira Components or labels) from a buried bullet to an up-front best practice in the Multi-repo polling section introduction. Fixed (1):
Tests: passedNext steps:
|
|
🤖 Finished Review · ✅ Success · Started 5:33 PM UTC · Completed 5:45 PM UTC Commit: |
|
🤖 Finished Retro · ✅ Success · Started 9:03 PM UTC · Completed 9:19 PM UTC Commit: |
Retro: PR #6103 — docs(#6094): add multi-repo polling section to Jira guideWorkflow chain: Issue #6094 → triage (4.5 min) → code (7.5 min) → review #1 (12 min, LGTM) → human feedback → fix (7 min) → review #2 (13 min, 1 low finding, approved) → human approval → merged. Outcome: Clean workflow. Docs-only PR, 1 file changed, 41 lines added. Two commits (original + fix addressing human editorial feedback). Merged in one fix iteration. Observations
No new proposalsAll observations map to existing open issues. No new proposals warranted. |
1 participant
Summary
Adds a "Multi-repo polling" section to the Jira integration guide (
docs/guides/user/jira-integration.md) addressing deployment questions identified during ROSAENG onboarding. The section covers whether each repo needs its own poll workflow, how entity property locks namespace across repos, and how the 50-candidate cap interacts with multiple pollers.Related Issue
Split from #6076; related to #5903 (backfill window documentation).
Changes
--target-repocontrols entity property namespace and GHA concurrency group isolationTesting
lycheelink checker passes — all 15 links in the file resolve correctlyscan-secrets)gitlintpasses on the commit messageCloses #6094
Post-script verification
agent/6094-multi-repo-polling-docs)d62fc7141712252d51853fa6a9be5af6b929251b..HEAD)