POST /rest/api/2/issue/bulk
Creates upto 50 issues and, where the option to create subtasks is enabled in Jira, subtasks. Transitions may be applied, to move the issues or subtasks to a workflow step other than the default start step, and issue properties set.
The content of each issue or subtask is defined using update and fields. The fields that can be set in the issue or subtask are determined using the Get create issue metadata. These are the same fields that appear on the issues' create screens.
Creating a subtask differs from creating an issue as follows:
issueTypemust be set to a subtask issue type (use Get create issue metadata to find subtask issue types).parentthe must contain the ID or key of the parent issue.
Permissions required: Browse projects and Create issues project permissions for the project in which each issue or subtask is created.
Servers
- https://your-domain.atlassian.net
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
issueUpdates[] |
Array | No | |
issueUpdates[].properties[] |
Array | No |
Details of issue properties to be add or update. |
issueUpdates[].properties[].key |
String | No |
The key of the property. Required on create and update. |
issueUpdates[].properties[].value |
No |
The value of the property. Required on create and update. |
|
issueUpdates[].fields |
Object | No |
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 |
issueUpdates[].update |
Object | No |
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 |
issueUpdates[].update.name |
Object | No |
Details of an operation to perform on a field. |
issueUpdates[].update.name.edit |
No |
The value to edit in the field. |
|
issueUpdates[].update.name.remove |
No |
The value to removed from the field. |
|
issueUpdates[].update.name.copy |
No |
The field value to copy from another issue. |
|
issueUpdates[].update.name.set |
No |
The value to set in the field. |
|
issueUpdates[].update.name.add |
No |
The value to add to the field. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.