Closed
feat(set_issue_field): handle builtin issue properties (body, title) via REST API#44152
Conversation
When field_name is "body" or "title", use REST API issues.update() instead of the custom project fields GraphQL API. This prevents the handler from failing when an agent uses set_issue_field to update built-in issue properties. Investigated run 28850818943: the Codex agent chose field_name="body" instead of selecting from available custom project fields when testing set_issue_field. With this change the action succeeds gracefully. Also update the tool description to mention builtin field support, so agents are more likely to use it correctly going forward. Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
feat: add builtin field support (body/title) to set_issue_field handler
feat(set_issue_field): handle builtin issue properties (body, title) via REST API
Jul 8, 2026
Copilot created this pull request from a session on behalf of
pelikhan
July 8, 2026 02:06
View session
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.
The
set_issue_fieldhandler only knew about custom project fields (GraphQLissueFields). When the Codex agent producedfield_name: "body"— a built-in REST property — it failed with "Issue field 'body' not found."Changes
set_issue_field.cjs: AddedBUILTIN_ISSUE_FIELDS = {"body", "title"}. Whenfield_namematches a builtin, skip GraphQL discovery entirely and callissues.update()directly.allowed_fieldsvalidation still applies; matching is case-insensitive.set_issue_field.test.cjs: 5 new tests coveringbody,title, case-insensitivity,allowed_fieldsrestriction, and wildcard passthrough.safe_outputs_tools.json(both copies): Updatedset_issue_fielddescription to surface builtin field support to agents, reducing hallucination of builtin names as custom fields.