SAP Cloud Platform Open Connectors

Jira On Prem Bulk

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.

Note: SAP Cloud Platform Open Connectors leverages the native provider bulk endpoints whenever available. When there is no bulk available from the provider, SAP Cloud Platform Open Connectors provides a bulk service for uploading and downloading data from the endpoint. See Bulk Details for the type of bulk used.

Bulk Details

Bulk InformationDetails
Bulk TypeSAP Cloud Platform Open Connectors bulk service and not native bulk endpoints. Rate limits come into play when using the SAP Cloud Platform Open Connectors bulk service, so review the limitations in the API provider's documentation.
Upsert SupportYes. For selected resources -/projects, /agents, /groups and /Incidents  
Field Selection SupportNo. To limit the fields returned by the query, you must use a transformation. For example, you can use only select * for this connector.
Order By SupportNo.

Extensions

Perform Bulk Upload for incidentSubtasks

Here's how you can perform a bulk upload for the object type incidentSubtasks 

  1. Create a file with the appropriate json or csv file extension. For example, incidentSubtasks.json.
  2. In case of uploading a csv file, convert the json to appropriate csv notation. 
  3. 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
       }
    }
  4. In the above payload, add the parent id of the incident and incidents as the objectName.

Hash Verification

If you configured the Callback Notification Signature Key (event.notification.signature.key) when you authenticated a connector 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.