---
title: "Update custom fields"
method: POST
path: "/rest/api/3/app/field/value"
tags: ["Issue custom field values (apps)"]
---

# Update custom fields

`POST /rest/api/3/app/field/value`

Updates the value of one or more custom fields on one or more issues. Combinations of custom field and issue should be unique within the request.

Apps can only perform this operation on [custom fields](https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/) and [custom field types](https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field-type/) declared in their own manifests.

**[Permissions](#permissions) required:** Only the app that owns the custom field or custom field type can update its values with this operation.

The new `write:app-data:jira` OAuth scope is 100% optional now, and not using it won't break your app. However, we recommend adding it to your app's scope list because we will eventually make it mandatory.

## Query parameters

- `generateChangelog` boolean
- `generateAppEvents` boolean

## Request body

- MultipleCustomFieldValuesUpdateDetails — List of updates for a custom fields.
  - `updates` MultipleCustomFieldValuesUpdate[]
    - `customField` string, required — The ID or key of the custom field. For example, `customfield_10010`.
    - `issueIds` integer[], required — The list of issue IDs.
    - `value` unknown, required

## Response `204`

Returned if the request is successful.

- unknown

## Other responses

- `400` — Returned if the request is invalid.
- `403` — Returned if the request is not authenticated as the app that provided all the fields.
- `404` — Returned if any field is not found.

---

[API](https://skmtc.net/atlassian/apis/the-jira-cloud-platform-rest-api-2.md) · [All operations](https://skmtc.net/atlassian/apis/the-jira-cloud-platform-rest-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/atlassian/the-jira-cloud-platform-rest-api-2/versions/5a51740d7ab3/schema)