ci: add fullsend Jira poll workflow - #15
Merged
Merged
Conversation
Add a scheduled GitHub Actions workflow that polls Jira for issue activity (comments, label changes) and dispatches fullsend agents, following the fullsend Jira integration guide. The poll runs every 5 minutes (plus manual workflow_dispatch), scoped to backplane-cli work in the ROSAENG project via --jql, and dispatches per-stage agent workflows found by their "# fullsend-stage:" marker. Requires repo secrets JIRA_TOKEN and JIRA_USER_EMAIL, and variable JIRA_BASE_URL to be configured. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
🤖 Finished Review · ✅ Success · Started 4:48 AM UTC · Completed 5:02 AM UTC Commit: |
|
Review skipped — this PR is already merged. The Posted by fullsend post-review check |
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
1 participant
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
Adds a scheduled GitHub Actions workflow (
.github/workflows/fullsend-poll-jira.yml) that connects fullsend to Jira, following the fullsend Jira integration guide.Each cycle the workflow runs
fullsend poll --input-driver jira-poll, which queries Jira for recently updated issues, detects new comments and label changes, converts them toNormalizedEvents, applies routing rules, and writes dispatch records. A dispatch step then triggers the matching per-stage agent workflow (matched by its# fullsend-stage:marker).Details
cron: */5 * * * *) plus manualworkflow_dispatch.--jira-project ROSAENGwith--jql 'project = ROSAENG AND component = "backplane-cli" AND status not in (Closed, Done) ORDER BY updated DESC'— bounded to backplane-cli work only.cancel-in-progress: falseso overlapping poll cycles queue rather than cancel (the primary safeguard against concurrent runs).${{ github.repository }}, which namespaces the Jira poll coordination state (lock / lastCheck entity properties).Required configuration (before enabling)
In Settings → Secrets and variables → Actions:
JIRA_TOKENJIRA_USER_EMAILJIRA_BASE_URLhttps://myteam.atlassian.netNotes / known limitations (from the guide)
Administrators→admin,Developers→write, else read), not by actual permissions.# fullsend-stage:marker; this repo currently uses the reusable-dispatch shim (fullsend.yaml), so dispatched Jira stages will no-op with a warning until matching stage workflows exist.🤖 Generated with Claude Code