...
The BulkOps app for Jira (Pro) can perform large amount of bulk operation as each task runs on the background. However, we have preset the current running job timeout for 30 minutes on any standard task. For longer jobs which require more time, we’ve set a specific high-load queue which should handle such tasks for a duration of 60 minutes. E.g. CSV uploads that contain 5k and above rows of data
Each file upload is limited to maximum of 2Mib of file storage
Please note that we do not store this file but temporarily need to create it for the contents to be read. After it has been created and processed, the file is deleted from our systems
The BulkOps app for Jira (Pro) works only on a site level and not on an organization level. Please understand this difference as you can use the features to delete users that you manage and not your managed users within your organization.
The performance of any bulk task depends on the response on your Atlassian instance environment, if your instance handles high load, the iteration will be much faster for the bulk operation you are running. If it’s not then it will reduce to your instance capability. This way, your operational task doesn’t cause excessive requests which ends up in a 429 error rate limit.
For example a typical bulk task of 4K rows for
bulk-create-usersorbulk-delete-userscan be done within 30 mins just to give you a benchmark.
When each bulk operation task is run and it has exceeded the time limit, you will receive an in-app message stating the
orStatus colour Red title failure
of the operation. In terms of the failure message, we’ll let you know the last row we finished reading, so the next file you upload can begin from the next row number.Status colour Green title success
...