Submission requirements
Problem summary
ado-aw has no supported way to set a native GitHub Issue Type (e.g. Bug / Feature / Task) on issues it files. The upstream gh-aw project exposes a first-class safe-outputs.set-issue-type (set or clear the issue type, max: 5) plus set-issue-field, but ado-aw (v0.45.1) has neither, and create-issue accepts only target-repo, title-prefix, labels, allowed-labels, assignees, max.
Impact: organizations that use native GitHub Issue Types as first-class work-item types cannot have agent-filed issues classified by type. Labels are not a substitute — Issue Types are a distinct, org-level field used for triage, filtering, and reporting. This is a parity gap with gh-aw.
Reproduction details
Environment: ado-aw 0.45.1 (Windows x64), Copilot engine, target: standalone.
1) set-issue-type safe output is not recognized:
ado-aw-debug:
set-issue-type:
type: Bug
create-issue:
target-repo: owner/repo
max: 1ado-aw compile →
Error: Failed to parse YAML front matter
Caused by:
unknown field `set-issue-type`, expected `skip-integrity` or `create-issue`
2) A type: / issue-type: field on create-issue is also rejected:
ado-aw-debug:
create-issue:
target-repo: owner/repo
issue-type: Bugado-aw compile →
unknown field `issue-type`, expected one of `target-repo`, `title-prefix`, `labels`, `allowed-labels`, `assignees`, `max`
Observed: no supported path to set a native Issue Type from an ado-aw workflow.
Expected: parity with gh-aw's set-issue-type (and ideally set-issue-field).
Workaround currently in use: file the issue with a routing label only, then a downstream pipeline stage mints a GitHub App installation token and calls PATCH /repos/{owner}/{repo}/issues/{number} with { "type": "Bug" }. This works but requires bespoke wiring outside the safe-output model, and the type is set after the injection-scanned create rather than as part of it.
Proposed next step
Port gh-aw's set-issue-type safe output to ado-aw (and ideally set-issue-field), and/or accept an optional type: on create-issue. Suggested area: safe-output handlers + front-matter schema for the GitHub-issue outputs. Reference: gh-aw docs — reference/safe-outputs/#set-issue-type-set-issue-type.
Posted by Copilot CLI assistant.
Submission requirements
.github/agents/ado-aw.agent.md.githubnext/ado-aw.Problem summary
ado-aw has no supported way to set a native GitHub Issue Type (e.g.
Bug/Feature/Task) on issues it files. The upstream gh-aw project exposes a first-classsafe-outputs.set-issue-type(set or clear the issue type,max: 5) plusset-issue-field, but ado-aw (v0.45.1) has neither, andcreate-issueaccepts onlytarget-repo,title-prefix,labels,allowed-labels,assignees,max.Impact: organizations that use native GitHub Issue Types as first-class work-item types cannot have agent-filed issues classified by type. Labels are not a substitute — Issue Types are a distinct, org-level field used for triage, filtering, and reporting. This is a parity gap with gh-aw.
Reproduction details
Environment:
ado-aw 0.45.1(Windows x64), Copilot engine,target: standalone.1)
set-issue-typesafe output is not recognized:ado-aw compile→2) A
type:/issue-type:field oncreate-issueis also rejected:ado-aw compile→Observed: no supported path to set a native Issue Type from an ado-aw workflow.
Expected: parity with gh-aw's
set-issue-type(and ideallyset-issue-field).Workaround currently in use: file the issue with a routing label only, then a downstream pipeline stage mints a GitHub App installation token and calls
PATCH /repos/{owner}/{repo}/issues/{number}with{ "type": "Bug" }. This works but requires bespoke wiring outside the safe-output model, and the type is set after the injection-scanned create rather than as part of it.Proposed next step
Port gh-aw's
set-issue-typesafe output to ado-aw (and ideallyset-issue-field), and/or accept an optionaltype:oncreate-issue. Suggested area: safe-output handlers + front-matter schema for the GitHub-issue outputs. Reference: gh-aw docs —reference/safe-outputs/#set-issue-type-set-issue-type.Posted by Copilot CLI assistant.