@com.adaptavist.hapi.cloud.analytics.CloudTracked class IssueUpdateDelegate extends AbstractCommentableIssueDelegate<java.util.Map<java.lang.String, com.atlassian.jira.rest.clientv2.model.FieldMetadata>, com.atlassian.jira.rest.clientv2.model.FieldMetadata>
A delegate for managing updates to an existing issue in Jira Cloud.
This class provides a structured way to update issue fields.
Example Usage:
// Update an issue's fields and add a comment
Issues.getByKey('TEST-123').update {
summary = 'Updated summary';
setComment('This is a new comment on the issue.');
}You can interact with issue metadata, modify standard or custom fields, and add comments as part of the update operation.
| Modifiers | Name | Description |
|---|---|---|
protected boolean |
skipScreenCheck |
| Constructor and description |
|---|
IssueUpdateDelegate(java.lang.String issueKey, Issue originalIssue) |
| Type Params | Return Type | Name and description |
|---|---|---|
|
protected java.lang.String |
getCustomFieldErrorMessage(java.lang.Object field) |
|
java.util.Map<java.lang.String, com.atlassian.jira.rest.clientv2.model.FieldMetadata> |
getMetaDatas() |
|
void |
setSkipScreenCheck(boolean skip)Sets whether to skip screen security checks when setting custom field values. |
Sets whether to skip screen security checks when setting custom field values.
When set to true, this allows setting custom field values even if they are not visible on the current screen. This is useful when you need to set fields that are hidden by screen security but are still valid for the issue.
Usage Example:
issue.update {
setSkipScreenCheck(true)
setCustomFieldValue("Hidden Field", "value")
}skip - true to allow a field to be set when it is not on the screen, false to prevent the operation