Atlassian: Remove fields associated with field schemes
Atlassian fieldSchemes.removeFieldsAssociatedWithSchemes: arguments, response, policy and SDK examples.
← Field schemes operations · Get started
Operation atlassian.removefieldsassociatedwithschemes
Provider route: DELETE /{cloudId}/rest/api/3/config/fieldschemes/fields. 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["fieldSchemes"]["removeFieldsAssociatedWithSchemes"]>[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.fieldSchemes.removeFieldsAssociatedWithSchemes(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.field_schemes.remove_fields_associated_with_schemes(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 | object | Required within parent | Additional keys: see wildcard field |
body.* | Model | Additional keys | Expand Remove fields associated with field schemes — request body — body value |
Referenced models: Remove fields associated with field schemes — request body — body value
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 | |
$ (anyOf 1) | JSON | Alternative | |
$ (anyOf 1) (anyOf 1) | Model | Alternative | Expand Remove fields associated with field schemes — response body — value results |
$ (anyOf 1) (anyOf 2) | Model | Alternative | Expand Remove fields associated with field schemes — response body — value results |
$ (anyOf 2) | null | Alternative |
Referenced models: Remove fields associated with field schemes — response body — value results
Schemas
Section titled “Schemas”Remove fields associated with field schemes — response body — value results
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Minimal response for updating field scheme to fields associations. |
results | JSON | Optional | |
results (anyOf 1) | array | Alternative | Unique items: true |
results (anyOf 1)[] | Model | Each item | Expand Remove fields associated with field schemes — response body — value results results array item |
results (anyOf 2) | null | Alternative |
Referenced models: Remove fields associated with field schemes — response body — value results results array item
Remove fields associated with field schemes — request body — body value
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Request item for removing field associations. write Only: true Additional keys: not allowed |
schemeIds | array | Required within parent | Set of scheme IDs from which to remove field associations Unique items: true |
schemeIds[] | integer | Each item | Set of scheme IDs from which to remove field associations Format: int64 |
Remove fields associated with field schemes — response body — value results results array item
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Minimal partial failure result when updating field scheme to fields associations. |
error | JSON | Optional | |
error (anyOf 1) | string | Alternative | |
error (anyOf 2) | null | Alternative | |
fieldId | JSON | Optional | |
fieldId (anyOf 1) | string | Alternative | |
fieldId (anyOf 2) | null | Alternative | |
schemeId | JSON | Optional | |
schemeId (anyOf 1) | JSON | Alternative | |
schemeId (anyOf 1) (anyOf 1) | integer | Alternative | Format: int64 |
schemeId (anyOf 1) (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
schemeId (anyOf 2) | null | Alternative | |
success | JSON | Optional | |
success (anyOf 1) | boolean | Alternative | |
success (anyOf 2) | null | Alternative |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: atlassian.removefieldsassociatedwithschemes. Catalog operation: removefieldsassociatedwithschemes. 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"]
No-content response statuses: [204]