Atlassian: Bulk create issue
Atlassian issues.createIssues: arguments, response, policy and SDK examples.
← Issues operations · Get started
Operation atlassian.createissues
Provider route: POST /{cloudId}/rest/api/3/issue/bulk. 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["issues"]["createIssues"]>[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.issues.createIssues(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.issues.create_issues(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 Bulk create issue — request body — body |
Referenced models: Bulk create issue — 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 |
|---|---|---|---|
$ | Model | Root | Expand Bulk create issue — response body |
Referenced models: Bulk create issue — response body
Schemas
Section titled “Schemas”13 more schemas are linked from the tables above, on the schema pages.
Bulk create issue — request body — body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: allowed |
issueUpdates | array | Optional | |
issueUpdates[] | Model | Each item | Expand Edit issue — request body — body |
Referenced models: Edit issue — request body — body
Bulk create issue — response body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Details about the issues created and the errors for requests that failed. |
errors | JSON | Optional | |
errors (anyOf 1) | array | Alternative | Error details for failed issue creation requests. Read only: true |
errors (anyOf 1)[] | Model | Each item | Expand Bulk create issue — response body — errors Error details for failed issue creation requests item |
errors (anyOf 2) | null | Alternative | |
issues | JSON | Optional | |
issues (anyOf 1) | array | Alternative | Details of the issues created. Read only: true |
issues (anyOf 1)[] | Model | Each item | Expand Create issue — response body |
issues (anyOf 2) | null | Alternative |
Referenced models: Bulk create issue — response body — errors Error details for failed issue creation requests item, Create issue — response body
Edit issue — request body — body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Details of an issue update request. Additional keys: allowed |
fields | object | Optional | List of issue screen fields to update, specifying the sub-field to update and its value for each field. This field provides a straightforward option when setting a sub-field. When multiple sub-fields or other operations are required, use `update`. Fields included in here cannot be included in `update`. Additional keys: see wildcard field |
fields.* | JSON | Additional keys | |
historyMetadata | Model | Optional | Expand Edit issue — request body — body history Metadata Additional issue history details. |
properties | array | Optional | Details of issue properties to be add or update. |
properties[] | Model | Each item | Expand Edit issue — request body — body properties item |
transition | Model | Optional | Expand Edit issue — request body — body transition Details of a transition. Required when performing a transition, optional when creating or editing an issue. |
update | object | Optional | A Map containing the field field name and a list of operations to perform on the issue screen field. Note that fields included in here cannot be included in `fields`. Additional keys: see wildcard field |
update.* | array | Additional keys | |
update.*[] | Model | Each item | Expand Edit issue — request body — body update value item |
Referenced models: Edit issue — request body — body properties item, Edit issue — request body — body update value item, Edit issue — request body — body history Metadata, Edit issue — request body — body transition
Bulk create issue — response body — errors Error details for failed issue creation requests item
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
elementErrors | JSON | Optional | |
elementErrors (anyOf 1) | Model | Alternative | Expand Validate project key — response body |
elementErrors (anyOf 2) | null | Alternative | |
failedElementNumber | JSON | Optional | |
failedElementNumber (anyOf 1) | JSON | Alternative | |
failedElementNumber (anyOf 1) (anyOf 1) | integer | Alternative | Format: int32 |
failedElementNumber (anyOf 1) (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
failedElementNumber (anyOf 2) | null | Alternative | |
status | JSON | Optional | |
status (anyOf 1) | JSON | Alternative | |
status (anyOf 1) (anyOf 1) | integer | Alternative | Format: int32 |
status (anyOf 1) (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
status (anyOf 2) | null | Alternative |
Referenced models: Validate project key — response body
Create issue — response body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Details about a created issue or subtask. |
id | JSON | Optional | |
id (anyOf 1) | string | Alternative | The ID of the created issue or subtask. Read only: true |
id (anyOf 2) | null | Alternative | |
key | JSON | Optional | |
key (anyOf 1) | string | Alternative | The key of the created issue or subtask. Read only: true |
key (anyOf 2) | null | Alternative | |
self | JSON | Optional | |
self (anyOf 1) | string | Alternative | The URL of the created issue or subtask. Read only: true |
self (anyOf 2) | null | Alternative | |
transition | JSON | Optional | |
transition (anyOf 1) | Model | Alternative | Expand Create issue — response body — watchers error Collection, status, warning Collection The response code and messages related to any requested transition. Read only: true |
transition (anyOf 2) | null | Alternative | |
watchers | JSON | Optional | |
watchers (anyOf 1) | Model | Alternative | Expand Create issue — response body — watchers error Collection, status, warning Collection The response code and messages related to any requested watchers. Read only: true |
watchers (anyOf 2) | null | Alternative |
Referenced models: Create issue — response body — watchers error Collection, status, warning Collection
Edit issue — request body — body properties item
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | An entity property, for more information see [Entity properties](https://developer.atlassian.com/cloud/jira/platform/jira-entity-properties/). Additional keys: not allowed |
key | string | Optional | The key of the property. Required on create and update. |
value | JSON | Optional | The value of the property. Required on create and update. |
Edit issue — request body — body update value item
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Details of an operation to perform on a field. Additional keys: not allowed |
add | JSON | Optional | The value to add to the field. |
copy | JSON | Optional | The field value to copy from another issue. |
edit | JSON | Optional | The value to edit in the field. |
remove | JSON | Optional | The value to removed from the field. |
set | JSON | Optional | The value to set in the field. |
Edit issue — request body — body history Metadata
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Details of issue history metadata. Additional keys: allowed |
activityDescription | string | Optional | The activity described in the history record. |
activityDescriptionKey | string | Optional | The key of the activity described in the history record. |
actor | Model | Optional | Expand Edit issue — request body — body history Metadata actor Details of the user whose action created the history record. |
cause | Model | Optional | Expand Edit issue — request body — body history Metadata actor Details of the cause that triggered the creation the history record. |
description | string | Optional | The description of the history record. |
descriptionKey | string | Optional | The description key of the history record. |
emailDescription | string | Optional | The description of the email address associated the history record. |
emailDescriptionKey | string | Optional | The description key of the email address associated the history record. |
extraData | object | Optional | Additional arbitrary information about the history record. Additional keys: see wildcard field |
extraData.* | string | Additional keys | |
generator | Model | Optional | Expand Edit issue — request body — body history Metadata actor Details of the system that generated the history record. |
type | string | Optional | The type of the history record. |
Referenced models: Edit issue — request body — body history Metadata actor
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: atlassian.createissues. Catalog operation: createissues. 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: ["write:jira-work"]