Creates a workflow. You can define transition rules using the shapes detailed in the following sections. If no transitional rules are specified the default system transition rules are used. Note: This only applies to company-managed scoped workflows. Use bulk create workflows to create both team and company-managed scoped workflows.
Permissions required: Administer Jira global permission.
Optionalcallback: undefinedCreate workflows and related statuses.
Permissions required:
Create workflows and related statuses.
Permissions required:
Optionalcallback: undefinedDeletes a workflow.
The workflow cannot be deleted if it is:
Permissions required: Administer Jira global permission.
Deletes a workflow.
The workflow cannot be deleted if it is:
Permissions required: Administer Jira global permission.
Optionalcallback: undefinedReturns a page of projects using a given workflow.
Returns a page of projects using a given workflow.
Optionalcallback: undefinedReturns a page of issue types using a given workflow within a project.
Returns a page of issue types using a given workflow within a project.
Optionalcallback: undefinedReturns a page of workflow schemes using a given workflow.
Returns a page of workflow schemes using a given workflow.
Optionalcallback: undefinedReturns a paginated list of published classic workflows. When workflow names are specified, details of those workflows are returned. Otherwise, all published classic workflows are returned.
This operation does not return next-gen workflows.
Permissions required: Administer Jira global permission.
Returns a paginated list of published classic workflows. When workflow names are specified, details of those workflows are returned. Otherwise, all published classic workflows are returned.
This operation does not return next-gen workflows.
Permissions required: Administer Jira global permission.
Optionalparameters: Version2Parameters.GetWorkflowsPaginatedOptionalcallback: undefinedReturns a list of workflows and related statuses by providing workflow names, workflow IDs, or project and issue types.
Permissions required:
Returns a list of workflows and related statuses by providing workflow names, workflow IDs, or project and issue types.
Permissions required:
Optionalcallback: undefinedReturns a paginated list of global and project workflows. If workflow names are specified in query string, details of those workflows are returned. Otherwise, all workflows are returned.
Permissions required:
Returns a paginated list of global and project workflows. If workflow names are specified in query string, details of those workflows are returned. Otherwise, all workflows are returned.
Permissions required:
Optionalparameters: Version2Parameters.SearchWorkflowsOptionalcallback: undefinedUpdate workflows and related statuses.
Permissions required:
Update workflows and related statuses.
Permissions required:
Optionalcallback: undefinedValidate the payload for bulk create workflows.
Permissions required:
Validate the payload for bulk create workflows.
Permissions required:
Optionalcallback: undefinedValidate the payload for bulk update workflows.
Permissions required:
Validate the payload for bulk update workflows.
Permissions required:
Optionalcallback: undefinedGet the list of workflow capabilities for a specific workflow using either the workflow ID, or the project and issue type ID pair. The response includes the scope of the workflow, defined as global/project-based, and a list of project types that the workflow is scoped to. It also includes all rules organised into their broad categories (conditions, validators, actions, triggers, screens) as well as the source location (Atlassian-provided, Connect, Forge).
Permissions required:
Get the list of workflow capabilities for a specific workflow using either the workflow ID, or the project and issue type ID pair. The response includes the scope of the workflow, defined as global/project-based, and a list of project types that the workflow is scoped to. It also includes all rules organised into their broad categories (conditions, validators, actions, triggers, screens) as well as the source location (Atlassian-provided, Connect, Forge).
Permissions required:
Optionalcallback: undefined
Creates a workflow. You can define transition rules using the shapes detailed in the following sections. If no transitional rules are specified the default system transition rules are used. Note: This only applies to company-managed scoped workflows. Use bulk create workflows to create both team and company-managed scoped workflows.
Permissions required: Administer Jira global permission.