문제 필드 값에 대한 REST API 엔드포인트
REST API를 사용하여 문제에 대한 문제 필드 값을 보고 관리합니다.
List issue field values for an issue
Lists all issue field values for an issue.
"List issue field values for an issue"에 대한 세분화된 액세스 토큰
이 엔드포인트는 다음 세분화된 토큰 형식에서 작동합니다.:
세분화된 토큰은 필수 권한 집합을 포함해야 합니다.:
- "Issues" repository permissions (read)
공용 리소스만 요청되는 경우 인증 또는 앞서 언급한 권한 없이 이 엔드포인트를 사용할 수 있습니다.
"List issue field values for an issue"에 대한 매개 변수
| 이름, 유형, 설명 |
|---|
accept string Setting to |
| 이름, 유형, 설명 |
|---|
owner string 필수The account owner of the repository. The name is not case sensitive. |
repo string 필수The name of the repository without the |
issue_number integer 필수The number that identifies the issue. |
| 이름, 유형, 설명 |
|---|
per_page integer The number of results per page (max 100). For more information, see "Using pagination in the REST API." 기본값: |
page integer The page number of the results to fetch. For more information, see "Using pagination in the REST API." 기본값: |
"List issue field values for an issue"에 대한 HTTP 응답 상태 코드
| 상태 코드 | 설명 |
|---|---|
200 | OK |
301 | Moved permanently |
404 | Resource not found |
410 | Gone |
"List issue field values for an issue"에 대한 코드 샘플
GHE.com에서 GitHub에 액세스하는 경우 api.github.com을 api.SUBDOMAIN.ghe.com의 엔터프라이즈 전용 하위 도메인으로 바꾸세요.
요청 예제
curl -L \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2026-03-10" \
https://api.github.com/repos/OWNER/REPO/issues/ISSUE_NUMBER/issue-field-valuesResponse
Status: 200[
{
"issue_field_id": 1,
"node_id": "IFT_GDKND",
"data_type": "text",
"value": "DRI"
},
{
"issue_field_id": 2,
"node_id": "IFSS_SADMS",
"data_type": "single_select",
"value": 1,
"single_select_option": {
"id": 1,
"name": "High",
"color": "red"
}
},
{
"issue_field_id": 3,
"node_id": "IFN_POINTS",
"data_type": "number",
"value": 42
},
{
"issue_field_id": 4,
"node_id": "IFD_DUEDATE",
"data_type": "date",
"value": "2025-12-25"
}
]Add issue field values to an issue
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 fieldssingle_select: Option names for single-select fields (must match an existing option name)number: Numeric values for number fieldsdate: 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. Creating content too quickly using this endpoint may result in secondary rate limiting. For more information, see "Rate limits for the API" and "Best practices for using the REST API."
"Add issue field values to an issue"에 대한 세분화된 액세스 토큰
이 엔드포인트는 다음 세분화된 토큰 형식에서 작동합니다.:
세분화된 토큰에는 다음 권한 집합 중 하나 이상이 있어야 합니다.:
- "Issues" repository permissions (write)
- "Pull requests" repository permissions (write)
"Add issue field values to an issue"에 대한 매개 변수
| 이름, 유형, 설명 |
|---|
accept string Setting to |
| 이름, 유형, 설명 |
|---|
repository_id integer 필수The unique identifier of the repository. |
issue_number integer 필수The number that identifies the issue. |
| 이름, 유형, 설명 | |||
|---|---|---|---|
issue_field_values array of objects An array of issue field values to add to this issue. Each field value must include the field ID and the value to set. | |||
Properties of |
| 이름, 유형, 설명 |
|---|
field_id integer 필수The ID of the issue field to set |
value string or number 필수The value to set for the field. The type depends on the field's data type:
|
"Add issue field values to an issue"에 대한 HTTP 응답 상태 코드
| 상태 코드 | 설명 |
|---|---|
200 | OK |
400 | Bad Request |
403 | Forbidden |
404 | Resource not found |
422 | Validation failed, or the endpoint has been spammed. |
503 | Service unavailable |
"Add issue field values to an issue"에 대한 코드 샘플
GHE.com에서 GitHub에 액세스하는 경우 api.github.com을 api.SUBDOMAIN.ghe.com의 엔터프라이즈 전용 하위 도메인으로 바꾸세요.
요청 예제
curl -L \
-X POST \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2026-03-10" \
https://api.github.com/repositories/REPOSITORY_ID/issues/ISSUE_NUMBER/issue-field-values \
-d '{"issue_field_values":[{"field_id":123,"value":"Critical"},{"field_id":456,"value":5},{"field_id":789,"value":"2024-12-31"}]}'Response
Status: 200[
{
"issue_field_id": 1,
"node_id": "IFT_GDKND",
"data_type": "text",
"value": "DRI"
},
{
"issue_field_id": 2,
"node_id": "IFSS_SADMS",
"data_type": "single_select",
"value": 1,
"single_select_option": {
"id": 1,
"name": "High",
"color": "red"
}
},
{
"issue_field_id": 3,
"node_id": "IFN_POINTS",
"data_type": "number",
"value": 42
},
{
"issue_field_id": 4,
"node_id": "IFD_DUEDATE",
"data_type": "date",
"value": "2025-12-25"
}
]Set issue field values for an issue
Set custom field values for an issue, replacing any existing values. You can set values for organization-level issue fields that have been defined for the repository's organization.
This endpoint supports the following field data types:
text: String values for text fieldssingle_select: Option names for single-select fields (must match an existing option name)number: Numeric values for number fieldsdate: ISO 8601 date strings for date fields
This operation will replace all existing field values with the provided ones. If you want to add field values without replacing existing ones, use the POST endpoint instead.
Only users with push access to the repository can set issue field values. If you don't have the proper permissions, you'll receive a 403 Forbidden response.
This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. For more information, see "Rate limits for the API" and "Best practices for using the REST API."
"Set issue field values for an issue"에 대한 세분화된 액세스 토큰
이 엔드포인트는 다음 세분화된 토큰 형식에서 작동합니다.:
세분화된 토큰에는 다음 권한 집합 중 하나 이상이 있어야 합니다.:
- "Issues" repository permissions (write)
- "Pull requests" repository permissions (write)
"Set issue field values for an issue"에 대한 매개 변수
| 이름, 유형, 설명 |
|---|
accept string Setting to |
| 이름, 유형, 설명 |
|---|
repository_id integer 필수The unique identifier of the repository. |
issue_number integer 필수The number that identifies the issue. |
| 이름, 유형, 설명 | |||
|---|---|---|---|
issue_field_values array of objects An array of issue field values to set for this issue. Each field value must include the field ID and the value to set. All existing field values will be replaced. | |||
Properties of |
| 이름, 유형, 설명 |
|---|
field_id integer 필수The ID of the issue field to set |
value string or number 필수The value to set for the field. The type depends on the field's data type:
|
"Set issue field values for an issue"에 대한 HTTP 응답 상태 코드
| 상태 코드 | 설명 |
|---|---|
200 | OK |
400 | Bad Request |
403 | Forbidden |
404 | Resource not found |
422 | Validation failed, or the endpoint has been spammed. |
503 | Service unavailable |
"Set issue field values for an issue"에 대한 코드 샘플
GHE.com에서 GitHub에 액세스하는 경우 api.github.com을 api.SUBDOMAIN.ghe.com의 엔터프라이즈 전용 하위 도메인으로 바꾸세요.
요청 예제
curl -L \
-X PUT \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2026-03-10" \
https://api.github.com/repositories/REPOSITORY_ID/issues/ISSUE_NUMBER/issue-field-values \
-d '{"issue_field_values":[{"field_id":123,"value":"Critical"},{"field_id":456,"value":5},{"field_id":789,"value":"2024-12-31"}]}'Response
Status: 200[
{
"issue_field_id": 1,
"node_id": "IFT_GDKND",
"data_type": "text",
"value": "DRI"
},
{
"issue_field_id": 2,
"node_id": "IFSS_SADMS",
"data_type": "single_select",
"value": 1,
"single_select_option": {
"id": 1,
"name": "High",
"color": "red"
}
},
{
"issue_field_id": 3,
"node_id": "IFN_POINTS",
"data_type": "number",
"value": 42
},
{
"issue_field_id": 4,
"node_id": "IFD_DUEDATE",
"data_type": "date",
"value": "2025-12-25"
}
]Delete an issue field value from an issue
Remove a specific custom field value from an issue.
Only users with push access to the repository can delete issue field values. If you don't have the proper permissions, you'll receive a 403 Forbidden response.
If the specified field does not have a value set on the issue, this operation will return a 404 error.
This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. For more information, see "Rate limits for the API" and "Best practices for using the REST API."
"Delete an issue field value from an issue"에 대한 세분화된 액세스 토큰
이 엔드포인트는 다음 세분화된 토큰 형식에서 작동합니다.:
세분화된 토큰에는 다음 권한 집합 중 하나 이상이 있어야 합니다.:
- "Issues" repository permissions (write)
- "Pull requests" repository permissions (write)
"Delete an issue field value from an issue"에 대한 매개 변수
| 이름, 유형, 설명 |
|---|
accept string Setting to |
| 이름, 유형, 설명 |
|---|
repository_id integer 필수The unique identifier of the repository. |
issue_number integer 필수The number that identifies the issue. |
issue_field_id integer 필수The unique identifier of the issue field. |
"Delete an issue field value from an issue"에 대한 HTTP 응답 상태 코드
| 상태 코드 | 설명 |
|---|---|
204 | Issue field value deleted successfully |
403 | Forbidden |
404 | Resource not found |
422 | Validation failed, or the endpoint has been spammed. |
503 | Service unavailable |
"Delete an issue field value from an issue"에 대한 코드 샘플
GHE.com에서 GitHub에 액세스하는 경우 api.github.com을 api.SUBDOMAIN.ghe.com의 엔터프라이즈 전용 하위 도메인으로 바꾸세요.
요청 예제
curl -L \
-X DELETE \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2026-03-10" \
https://api.github.com/repositories/REPOSITORY_ID/issues/ISSUE_NUMBER/issue-field-values/ISSUE_FIELD_IDIssue field value deleted successfully
Status: 204