[plan] Add issue fields support to create-issue safe output

[github-actions]

Objective

Extend the create-issue safe output to accept issue fields (e.g., custom fields like iteration, single-select, date, etc.) similar to how it currently handles labels.

Context

Issue fields are entering public preview on GitHub. Currently, safe outputs support labels and issue types but not issue fields. This is tracked in #30846.

Approach

1. Review the current create-issue safe output schema in actions/setup/js/ (the safeoutputs action)
2. Identify the API/MCP mechanism used for setting fields (see set_issue_fields in issues_granular.go)
3. Add an optional fields parameter to the create-issue safe output schema (modeled after the labels parameter)
4. Implement the field-setting logic after issue creation (similar to how labels are applied post-creation or inline)
5. Update schema validation and error handling

Files to Modify

• actions/setup/js/ — safe output action source (create-issue handler)
• schemas/ — update JSON schema for create-issue if applicable
• pkg/workflow/js/safe_outputs_tools.json — update tool definition

Acceptance Criteria

• create-issue safe output accepts an optional fields parameter
• Fields are applied when creating an issue
• Invalid field names/values produce actionable error messages
• Unit tests cover success and error cases
• Schema reference updated
  Related to Implement Issue Fields Support in Safe Outputs #30846

Generated by Plan Command for issue #30846 · ● 3.1M · ◷

• expires on May 9, 2026, 6:53 PM UTC