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-issue safe output to accept issue fields (e.g., as it currently does with labels).
- Investigate if the
update-issue safe output needs support for updating issue fields, similar to label operations.
- Propose the introduction of
set-issue-field (analogous to set-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:
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
View original Slack conversation
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:
create-issuesafe output to accept issue fields (e.g., as it currently does with labels).update-issuesafe output needs support for updating issue fields, similar to label operations.set-issue-field(analogous toset-issue-type), as well as how issue fields could be managed (add/remove/set) similarly to labels.set_issue_fields).Links & References:
Acceptance Criteria:
View original Slack conversation