OptionaldefaultWorkflowId?: stringThe ID of the workflow for issue types without having a mapping defined in this workflow scheme. Only used in
global-scoped workflow schemes. If the defaultWorkflowId isn't specified, this is set to Jira Workflow (jira).
The new description for this workflow scheme.
The ID of this workflow scheme.
The new name for this workflow scheme.
OptionalstatusMappingsByIssueTypeOverride?: {Overrides, for the selected issue types, any status mappings provided in statusMappingsByWorkflows. Status
mappings are required when the new workflow for an issue type doesn't contain all statuses that the old workflow
has. Status mappings can be provided by a combination of statusMappingsByWorkflows and
statusMappingsByIssueTypeOverride.
OptionalstatusMappingsByWorkflows?: {The status mappings by workflows. Status mappings are required when the new workflow for an issue type doesn't
contain all statuses that the old workflow has. Status mappings can be provided by a combination of
statusMappingsByWorkflows and statusMappingsByIssueTypeOverride.
Optionalid?: stringThe version UUID.
OptionalversionNumber?: numberThe version number.
OptionalworkflowsForIssueTypes?: { issueTypeIds: string[]; workflowId: string; [key: string]: unknown }[]Mappings from workflows to issue types.
Optionaloptions: RequestOptions
Updates company-managed and team-managed project workflow schemes. This API doesn't have a concept of draft, so any changes made to a workflow scheme are immediately available. When changing the available statuses for issue types, an asynchronous task migrates the issues as defined in the provided mappings.
Permissions required: