Jira Align 8.0 bulk import cancellation leaves partial data without rollback
0 reputation · 21 Feb 2025, 18:41 UTC
Current behavior
In Jira Align 8.0 the bulk import job endpoint (/jobs) accepts a cancel flag via POST /jobs/{id}/status. The UI can abort a job, but the API returns 405 for DELETE /jobs/{id}. When cancelled, the job status changes to cancelled while any records already written remain in the system.
Timeout constraints
Synchronous calls honor a client‑side timeout (recommended 30–60 s). Asynchronous bulk imports run on a background worker with a hard 120‑second limit that is not exposed to callers.
Unresolved decision
The 8.0 release notes mention a planned feature to allow partial rollback on cancellation, yet the decision remains open. It is unclear whether a future release will introduce a dedicated DELETE /jobs/{id} that fully aborts and rolls back the import transaction.
Will a future release provide a DELETE /jobs/{id} endpoint that rolls back partial imports? What is the expected timeline for exposing the background worker timeout to clients? How should integrators handle partial data left after cancellation today?
