feat(triage-flow): add ticket triage workflow and jira-write skill; release 3.1.12 - #332
Closed
sergepr wants to merge 2 commits into
Closed
feat(triage-flow): add ticket triage workflow and jira-write skill; release 3.1.12#332sergepr wants to merge 2 commits into
sergepr wants to merge 2 commits into
Conversation
…ipped profile Both assertions went stale in 2fcdce8 ("Bring back opus/sol to lightweight"), which changed the lightweight sources without updating the tests. They have been failing on main since: - profiles.test.ts expected the descriptor suffix to contain "lightweight profile"; the committed lightweight.json ships " (lightweight: simpler workflows, smaller models)". - profile.e2e.test.ts expected core-copilot-light's architect to resolve to "GPT-5.6 Sol"; 2fcdce8 put claude-opus-5-high at the head of the light architect list, so it now resolves to "Claude Opus 5". Tests updated to match the shipped profile; no source or generator change. Suite goes from 2 failed / 759 passed to 761 passed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…elease 3.1.12 Adds triage-flow: a caller-invoked workflow that triages one issue-tracker ticket — intake (redacted via data-collection), requirements elicitation through comment round-trips, and a posted assessment comment on completion. It never mutates ticket status or assignee. Golden source in instructions/r3/core: - workflows/triage-flow.md plus five phases (intake, elicitation, publish-questions, assess, completion-check) - skills/jira-write — write-capable counterpart to read-only data-collection: post a comment, transition, or reassign, after content-level safety checks Generated into all fourteen plugin builds (seven full, seven lightweight) and version bumped 3.1.11 -> 3.1.12 across every manifest and all three marketplaces, keeping full and light in lockstep as in prior releases. Deployment wiring for this repo's own use: .mcp.json (Atlassian MCP via headersHelper), agents/jira-mcp-auth-header.sh, agents/jira-triage.config.json. The Bearer token is not committed; agents/jira-triage.secrets.json is now gitignored, which the config file already claimed but .gitignore did not enforce. Scope limits, deliberate and recorded in the flow's out_of_scope section: caller-supplied ticket_key only, no scheduler, and writes_require_human_confirmation is false for this POC. Running triage-flow requires repo-side setup (agents/jira-triage.config.json, .mcp.json, a local secrets file); without the config the flow stops and reports rather than guessing values. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
sergepr
marked this pull request as ready for review
August 28, 2026 11:30
sergepr
requested review from
YevheniiaLementova,
isolomatov-gd and
omaiesh
as code owners
August 28, 2026 11:30
This was referenced Aug 28, 2026
Author
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.
What
Adds triage-flow: a caller-invoked workflow that triages one issue-tracker ticket — intake (redacted via
data-collection), requirements elicitation through comment round-trips, and a posted assessment comment on completion. It never mutates ticket status or assignee.Also adds the
jira-writeskill: the write-capable counterpart to read-onlydata-collection(post a comment, transition, reassign — after content-level safety checks).Release 3.1.11 → 3.1.12.
Commits
0b71725e22b8d5The test fix is first and standalone on purpose — it repairs breakage that predates this branch (see below), so it can be reviewed independently of the feature.
Changes
Golden source (
instructions/r3/core)workflows/triage-flow.md+ five phases: intake, elicitation, publish-questions, assess, completion-checkskills/jira-write/+ vendor-binding referenceGenerated output — all fourteen plugin builds (seven full, seven lightweight), version bumped across every manifest and all three marketplaces. Full and light stay in lockstep, as in prior releases.
Deployment wiring for this repo's own use —
.mcp.json(Atlassian MCP viaheadersHelper),agents/jira-mcp-auth-header.sh,agents/jira-triage.config.json.Pre-existing test breakage, fixed here
Two assertions went stale in 2fcdce8 ("Bring back opus/sol to lightweight"), which changed the lightweight sources without updating the tests. They have been failing on
mainsince — unrelated to triage-flow, butci-rosettify-pluginsfires on this PR (it touchessrc/rosettify-plugins/**), so they are fixed here to keep the gate green.profiles.test.tsexpected the descriptor suffix to contain"lightweight profile"; the committedlightweight.jsonships" (lightweight: simpler workflows, smaller models)".profile.e2e.test.tsexpectedcore-copilot-light's architect to resolve toGPT-5.6 Sol; 2fcdce8 putclaude-opus-5-highat the head of the light architect list, so it resolves toClaude Opus 5.Tests updated to match the shipped profile — no source or generator change. Suite goes from 2 failed / 759 passed to 761 passed; typecheck clean.
Security
agents/jira-triage.secrets.jsonis now gitignored. The config file already claimed it was, but.gitignoredid not enforce it — so the first person to follow the setup steps would have had a live Jira Bearer token stageable bygit add -A. No token is committed.Scope limits — deliberate, recorded in the flow's
out_of_scopeticket_keyonly; no schedulerwrites_require_human_confirmation: falsefor this POCagents/jira-triage.config.json,.mcp.json, a local secrets file). Without the config the flow stops and reports rather than guessing values.Reviewer notes
agents/jira-triage.config.jsoncarries a real service-account ID and the POC write-gate override. Intentional — flagging it since it lands in history.lightweight.jsoncurrently declares nomodelOverrides(removed in 2fcdce8). Left alone here; worth a separate cleanup.🤖 Generated with Claude Code