Bulk provides an option to upload a large number of resources, such as contacts, to a service provider all at once. You can use bulk to download a csv or json file from a large number of records or upload a csv or json file to add multiple records. See Using Bulk for more information on managing bulk.
Bulk Details
Bulk Information | Details |
---|---|
Bulk Type | Cloud Elements bulk service and not native bulk endpoints. Rate limits come into play when using the Cloud Elements bulk service, so review the limitations in the API provider's documentation. |
Upsert Support | Yes. For selected resources -/projects , /agents , /groups and /Incidents |
Field Selection Support | No. To limit the fields returned by the query, you must use a transformation. For example, you can use only select * for this element. |
Order By Support | No. |
Extensions
Perform Bulk Upload for incidentSubtasks
Here's how you can perform a bulk upload for the object type incidentSubtasks
- Create a file with the appropriate json or csv file extension. For example, incidentSubtasks.json.
- In case of uploading a csv file, convert the json to appropriate csv notation.
- The payload should look as shown below.
{ "fields": { "issuetype": { "description": "by Jira Service Desk.Created", "name": "Sub-task", "subtask": true }, "parent": { "id": "xxxxx" }, "description": "<DESCRIPTION>", "project": { "id": xxxxxxx }, "summary": "Jira Onprem Product Understanding", "reporter": { "name": "<USERNAME>" }, "priority": { "id": "xxxx" }, "labels": [ "xxxxxxxx" ], "assignee": null } }
In the above payload, add the
parent id
of the incident andincidents
as the objectName.
Hash Verification
If you configured the Callback Notification Signature Key (event.notification.signature.key
) when you authenticated an element instance, the bulk APIs will use the signature key to provide hash verification in the header of bulk jobs. For more information, see Hash Verification.