Skip to content

Atlassian: Reorder custom field options (context)

Atlassian issueCustomFieldOptions.reorderCustomFieldOptions: arguments, response, policy and SDK examples.

← Issue custom field options operations · Get started

Operation atlassian.reordercustomfieldoptions

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

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["issueCustomFieldOptions"]["reorderCustomFieldOptions"]>[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.issueCustomFieldOptions.reorderCustomFieldOptions(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_options.reorder_custom_field_options(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
pathobjectRequired within parentAdditional keys: not allowed
path.cloudIdstringRequired within parentPattern: ^[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.fieldIdstringRequired within parent
path.contextIdintegerRequired within parentFormat: int64
bodyModelRequired within parentExpand Reorder custom field options (context) — request body — body

Referenced models: Reorder custom field options (context) — request body — body

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$nullRoot
Reorder custom field options (context) — request body — body
FieldTypePresenceDescription and constraints
$objectRootAn ordered list of custom field option IDs and information on where to move them.
Additional keys: not allowed
afterstringOptionalThe ID of the custom field option or cascading option to place the moved options after. Required if `position` isn't provided.
write Only: true
customFieldOptionIdsarrayRequired within parentA list of IDs of custom field options to move. The order of the custom field option IDs in the list is the order they are given after the move. The list must contain custom field options or cascading options, but not both.
write Only: true
customFieldOptionIds[]stringEach itemwrite Only: true
positionstringOptionalThe position the custom field options should be moved to. Required if `after` isn't provided.
One of: First, Last
write Only: true

SDK function policy ID: atlassian.reordercustomfieldoptions. Catalog operation: reorderCustomFieldOptions. 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]

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.