Atlassian: Switch workflow scheme for project
Atlassian workflowSchemes.switchWorkflowSchemeForProject: arguments, response, policy and SDK examples.
← Workflow schemes operations · Get started
Operation atlassian.switchworkflowschemeforproject
Provider route: POST /{cloudId}/rest/api/3/workflowscheme/project/switch. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/atlassian with npm, or alter-sdk-atlassian with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { AtlassianIntegration } from "@alter-ai/atlassian";
async function execute(input: Parameters<AtlassianIntegration["workflowSchemes"]["switchWorkflowSchemeForProject"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new AtlassianIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.workflowSchemes.switchWorkflowSchemeForProject(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_atlassian import AtlassianIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = AtlassianIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.workflow_schemes.switch_workflow_scheme_for_project(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
path | object | Required within parent | Additional keys: not allowed |
path.cloudId | string | Required within parent | Pattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$ |
body | Model | Required within parent | Expand Switch workflow scheme for project — request body — body |
Referenced models: Switch workflow scheme for project — request body — body
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | JSON | Root |
Schemas
Section titled “Schemas”Switch workflow scheme for project — request body — body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Request to switch a project's workflow scheme Additional keys: allowed |
mappingsByIssueTypeOverride | array | Optional | The mappings for migrating issues from old statuses to new statuses when switching from one workflow scheme to another. This field is required if any statuses in the current project's workflows would no longer exist in the target workflow scheme. Each mapping defines how to update issues from an old status to the corresponding new status in the issue’s new workflow. |
mappingsByIssueTypeOverride[] | Model | Each item | Expand Switch workflow scheme for project — request body — body mappings By Issue Type Override item |
projectId | string | Optional | The ID of the project to switch the workflow scheme for |
targetSchemeId | string | Optional | The ID of the target workflow scheme to switch to |
Referenced models: Switch workflow scheme for project — request body — body mappings By Issue Type Override item
Switch workflow scheme for project — request body — body mappings By Issue Type Override item
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | The mappings for migrating issues from old statuses to new statuses when switching from one workflow scheme to another. This field is required if any statuses in the current project's workflows would no longer exist in the target workflow scheme. Each mapping defines how to update issues from an old status to the corresponding new status in the issue’s new workflow. Additional keys: not allowed |
issueTypeId | string | Optional | |
statusMappings | array | Optional | |
statusMappings[] | Model | Each item | Expand Update workflow scheme — request body — body status Mappings By Workflows item status Mappings item |
Referenced models: Update workflow scheme — request body — body status Mappings By Workflows item status Mappings item
Update workflow scheme — request body — body status Mappings By Workflows item status Mappings item
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
newStatusId | string | Optional | |
oldStatusId | string | Optional |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: atlassian.switchworkflowschemeforproject. Catalog operation: switchworkflowschemeforproject. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.
Required provider scopes: ["manage:jira-configuration"]