PUT
/project_portfolio_settings/{project_portfolio_setting_gid}Update a project portfolio setting
Updates an existing project portfolio setting. Supply the fields to change in data; unspecified fields remain unchanged, and is_access_control_inherited controls whether portfolio members gain access to the project. You must have the project_portfolio_settings:write scope to perform the update.
- RetriesRetries up to 2×, 500ms backoff, 30s timeout.
opt_fieldsarray<string>optional
Comma-separated properties to include in the response, including nested properties. Supported values include `created_at`, `is_access_control_inherited`, `portfolio`, and `project`.
The fields to update on the project portfolio setting.
dataobjectoptional
The project portfolio setting fields to update; omitted fields remain unchanged.
200Returns the complete updated project portfolio setting record.
dataobjectoptional
400Returned when a parameter is missing or malformed, or the request syntax is invalid.
errorsarray<object>optional
401Returned when the request does not include a valid authentication token.
errorsarray<object>optional
403Returned when the authenticated user does not have access to the project portfolio setting.
errorsarray<object>optional
404Returned when the requested action is not known or the project portfolio setting does not exist.
errorsarray<object>optional
500Returned when a server-side problem prevents the request from completing.
errorsarray<object>optional
Error handling
A 400 is returned when the request is missing or malformed, a 401 when no valid authentication token is provided, and a 403 when the authenticated user lacks access. A 404 is returned when the project portfolio setting does not exist, and a 500 for a server-side failure. The project_portfolio_settings:write scope is required, and is_access_control_inherited must be a boolean when supplied.