editIssue method
- required String issueIdOrKey,
- bool? notifyUsers,
- bool? overrideScreenSecurity,
- bool? overrideEditableFlag,
- required IssueUpdateDetails body,
Edits an issue. A transition may be applied and issue properties updated as part of the edit.
The edits to the issue's fields are defined using update
and fields
.
The fields that can be edited are determined using
Get edit issue metadata.
The parent field may be set by key or ID. For standard issue types, the
parent may be removed by setting update.parent.set.none
to true. Note
that the description
, environment
, and any textarea
type custom
fields (multi-line text fields) take Atlassian Document Format content.
Single line custom fields (textfield
) accept a string and don't handle
Atlassian Document Format content.
Connect apps having an app user with Administer Jira
global permission, and Forge
apps acting on behalf of users with Administer Jira
global permission, can
override the screen security configuration using overrideScreenSecurity
and overrideEditableFlag
.
This operation can be accessed anonymously.
Permissions required:
- Browse projects and Edit issues project permission for the project that the issue is in.
- If issue-level security is configured, issue-level security permission to view the issue.
Implementation
Future<dynamic> editIssue(
{required String issueIdOrKey,
bool? notifyUsers,
bool? overrideScreenSecurity,
bool? overrideEditableFlag,
required IssueUpdateDetails body}) async {
return await _client.send(
'put',
'rest/api/3/issue/{issueIdOrKey}',
pathParameters: {
'issueIdOrKey': issueIdOrKey,
},
queryParameters: {
if (notifyUsers != null) 'notifyUsers': '$notifyUsers',
if (overrideScreenSecurity != null)
'overrideScreenSecurity': '$overrideScreenSecurity',
if (overrideEditableFlag != null)
'overrideEditableFlag': '$overrideEditableFlag',
},
body: body.toJson(),
);
}