Updates an issue’s properties such as title, description, or labels. Permissions required: bb.issues.update
The list of fields to update.
If set to true, and the issue is not found, a new issue will be created.
In this situation, update_mask is ignored.
The name of the issue. Format: projects/{project}/issues/{issue}
The title of the issue.
The description of the issue.
TYPE_UNSPECIFIED, DATABASE_CHANGE, GRANT_REQUEST, DATABASE_EXPORT The status of the issue.
ISSUE_STATUS_UNSPECIFIED, OPEN, DONE, CANCELED The approval template for the issue.
The plan associated with the issue. Can be empty. Format: projects/{project}/plans/{plan}
The rollout associated with the issue. Can be empty. Format: projects/{project}/rollouts/{rollout}
Used if the issue type is GRANT_REQUEST.
The releasers of the pending stage of the issue rollout, judging from the rollout policy. Format:
The risk level of the issue.
RISK_LEVEL_UNSPECIFIED, LOW, MODERATE, HIGH The status count of the issue. Keys are the following:
Labels attached to the issue for categorization and filtering.
OK
The name of the issue. Format: projects/{project}/issues/{issue}
The title of the issue.
The description of the issue.
TYPE_UNSPECIFIED, DATABASE_CHANGE, GRANT_REQUEST, DATABASE_EXPORT The status of the issue.
ISSUE_STATUS_UNSPECIFIED, OPEN, DONE, CANCELED The approval template for the issue.
Format: users/[email protected]
The plan associated with the issue. Can be empty. Format: projects/{project}/plans/{plan}
The rollout associated with the issue. Can be empty. Format: projects/{project}/rollouts/{rollout}
Used if the issue type is GRANT_REQUEST.
The releasers of the pending stage of the issue rollout, judging from the rollout policy. Format:
The risk level of the issue.
RISK_LEVEL_UNSPECIFIED, LOW, MODERATE, HIGH The status count of the issue. Keys are the following:
Labels attached to the issue for categorization and filtering.
APPROVAL_STATUS_UNSPECIFIED, CHECKING, PENDING, APPROVED, REJECTED, SKIPPED, ERROR Only populated when approval_status == ERROR