---
title: "Add issue field values to an issue"
method: POST
path: "/repos/{owner}/{repo}/issues/{issue_number}/issue-field-values"
tags: ["issues"]
---

# Add issue field values to an issue

`POST /repos/{owner}/{repo}/issues/{issue_number}/issue-field-values`

Add custom field values to an issue. You can set values for organization-level issue fields that have been defined for the repository's organization.
Adding an empty array will clear all existing field values for the issue.

This endpoint supports the following field data types:
- **`text`**: String values for text fields
- **`single_select`**: Option names for single-select fields (must match an existing option name)
- **`number`**: Numeric values for number fields
- **`date`**: ISO 8601 date strings for date fields

Only users with push access to the repository can add issue field values. If you don't have the proper permissions, you'll receive a `403 Forbidden` response.

This endpoint triggers [notifications](https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. For more information, see "[Rate limits for the API](https://docs.github.com/rest/using-the-rest-api/rate-limits-for-the-rest-api#about-secondary-rate-limits)"
and "[Best practices for using the REST API](https://docs.github.com/rest/guides/best-practices-for-using-the-rest-api)."

## Path parameters

- `owner` string, required
- `repo` string, required
- `issue_number` integer, required

## Request body

- object
  - `issue_field_values` object[] — An array of issue field values to add to this issue. Each field value must include the field ID and the value to set.
    - `field_id` integer, required — The ID of the issue field to set
    - `value` union, required — The value to set for the field. The type depends on the field's data type: - For text fields: provide a string value - For single_select fields: provide the option name as a string (must match an existing option) - For number fields: provide a numeric value - For multi_select fields: provide an array of option names (must match existing options) - For date fields: provide an ISO 8601 date string
      - string — The value to set for text, single_select, or date fields
      - number — The value to set for number fields
      - string[] — The value to set for multi_select fields (array of option names)

## Response `200`

Response

- IssueFieldValue[] — The current issue field values for this issue after adding the new values
  - `issue_field_id` integer, required — Unique identifier for the issue field.
  - `issue_field_name` string — The human-readable name of the issue field.
  - `node_id` string, required
  - `data_type` 'text' | 'single_select' | 'multi_select' | 'number' | 'date', required — The data type of the issue field
  - `value` union, required — The value of the issue field
    - string
    - number
    - integer
  - `single_select_option` object, nullable — Details about the selected option (only present for single_select fields)
    - `id` integer, required — Unique identifier for the option.
    - `name` string, required — The name of the option
    - `color` string, required — The color of the option
  - `multi_select_options` object[], nullable — Details about the selected options
    - `id` integer, required — Unique identifier for the option.
    - `name` string, required — The name of the option
    - `color` string, required — The color of the option

## Other responses

- `400` — Bad Request
- `403` — Forbidden
- `404` — Resource not found
- `422` — Validation failed, or the endpoint has been spammed.
- `503` — Service unavailable

---

[API](https://skmtc.net/github/apis/rest-api.md) · [All operations](https://skmtc.net/github/apis/rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/github/rest-api/versions/80850db290cd/schema)