Atlassian: Create custom field context

← Issue custom field contexts operations · Get started

Operation atlassian.createcustomfieldcontext

Provider route: POST /{cloudId}/rest/api/3/field/{fieldId}/context. Alter supplies the connection’s credentials and routing.

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["issueCustomFieldContexts"]["createCustomFieldContext"]>[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.issueCustomFieldContexts.createCustomFieldContext(input);
    const result = await call.wait();
    return result.bodyJson();
  } finally {
    await app.close();
  }
}

import os
from alter_sdk import App
from 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.issue_custom_field_contexts.create_custom_field_context(arguments)
        result = await call.wait()
        return result.body_json()

Input

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}$
path.fieldId	string	Required within parent
body	Model	Required within parent	Expand Create custom field context — request body — body

Referenced models: Create custom field context — request body — body

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
$	Model	Root	Expand Create custom field context — response body

Referenced models: Create custom field context — response body

Schemas

Create custom field context — request body — body

Field	Type	Presence	Description and constraints
$	object	Root	The details of a created custom field context. Additional keys: not allowed
description	string	Optional	The description of the context.
id	string	Optional	The ID of the context. Read only: true
issueTypeIds	array	Optional	The list of issue types IDs for the context. If the list is empty, the context refers to all issue types.
issueTypeIds[]	string	Each item
name	string	Required within parent	The name of the context.
projectIds	array	Optional	The list of project IDs associated with the context. If the list is empty, the context is global.
projectIds[]	string	Each item

Create custom field context — response body

Field	Type	Presence	Description and constraints
$	object	Root	The details of a created custom field context.
description	JSON	Optional
description (anyOf 1)	string	Alternative	The description of the context.
description (anyOf 2)	null	Alternative
id	JSON	Optional
id (anyOf 1)	string	Alternative	The ID of the context. Read only: true
id (anyOf 2)	null	Alternative
issueTypeIds	JSON	Optional
issueTypeIds (anyOf 1)	array	Alternative	The list of issue types IDs for the context. If the list is empty, the context refers to all issue types.
issueTypeIds (anyOf 1)[]	string	Each item
issueTypeIds (anyOf 2)	null	Alternative
name	JSON	Optional
name (anyOf 1)	string	Alternative	The name of the context.
name (anyOf 2)	null	Alternative
projectIds	JSON	Optional
projectIds (anyOf 1)	array	Alternative	The list of project IDs associated with the context. If the list is empty, the context is global.
projectIds (anyOf 1)[]	string	Each item
projectIds (anyOf 2)	null	Alternative

Policy, approvals and errors

SDK function policy ID: atlassian.createcustomfieldcontext. Catalog operation: createCustomFieldContext. 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"]

Official provider source