Repository navigation
Implement Issue Fields Support in Safe Outputs #30846
Description
Currently, safe outputs in gh-aw support labels and issue types, but do not provide native support for issue fields. With Issue fields entering public preview, users will expect the ability to use these within automated workflows (AW), including during triage and create/update scenarios.
Goals:
- Update the
create-issuesafe output to accept issue fields (e.g., as it currently does with labels). - Investigate if the
update-issuesafe output needs support for updating issue fields, similar to label operations. - Propose the introduction of
set-issue-field(analogous toset-issue-type), as well as how issue fields could be managed (add/remove/set) similarly to labels. - Review https://github.github.com/gh-aw/reference/safe-outputs/#issue-creation-create-issue for the current schema, and expand accordingly.
- Research discovery mechanisms for available issue fields and values at the org level (refer to MCP tool functionality in issues_granular, e.g.,
set_issue_fields).
Links & References:
- Slack discussion
- Current reference
- Related field management sample: issues_granular.go
Acceptance Criteria:
- Users can set issue fields via safe outputs for both creation and update operations, matching or improving on current label handling
- Documentation and schema reference updated
Activity
pelikhan commentedon May 7, 2026
/plan review the proposal and generate separate issues for each goal.
github-actions commentedon May 7, 2026
✅ Plan Command completed successfully!
github-actions commentedon May 14, 2026
🎉 Automatically closed by Sub-Issue Closer
All sub-issues have been completed. This parent issue is now closed automatically.
Sub-issues status: 5/5 closed (100%)
pelikhan commentedon May 15, 2026
I think this is done.
labudis commentedon May 15, 2026
Hey! We're setting up issue fields support in our triage agent AW workflows and noticed that
set-issue-fieldand theissue_fieldstoolset are documented on the safe outputs reference, but the compiler (v0.72.1, latest) rejects both duringgh aw compile. Is this not shipped yet, or are we missing something? Happy to test once it's available.[community] Update community contributions in README