Jira Align 8.0 bulk import cancellation leaves partial data without rollback

Answer to the Core Question

As of Jira Align 8.0, POST /jobs/{id}/status?cancel=true merely flips the job state to cancelled. The system does not roll back any records that were already persisted. No DELETE /jobs/{id} endpoint exists in this release, and attempts to call it return 405 Method Not Allowed. Atlassian has announced a planned feature for “partial rollback on cancellation”, but no public roadmap or version number has been released that implements this capability. Until such a feature ships, integrators must treat the cancellation as a soft stop that preserves data.

What the Future Might Offer

While the 8.x release notes hint at a rollback mechanism, Atlassian has not committed to a specific release or API contract for a full DELETE /jobs/{id} that undoes all import work. The background worker’s 120‑second hard timeout is also not exposed to clients, so developers cannot adjust it to accommodate larger imports. In practice, this means:

• Future releases may introduce a transactional rollback, but no date is available.
• The worker timeout will likely remain internal, though future APIs might expose a configurable limit.

Practical Steps for Integrators Today

To avoid orphaned data after a cancellation, follow this workflow:

1. Query Job Status: Call GET /jobs/{id} to confirm the job is cancelled or failed.
2. Identify Imported Records: If the import payload includes a unique import‑job‑id or you can filter by the job’s creation timestamp, query the relevant tables (e.g., epic, feature) for rows linked to that ID.
3. Verify Persistence: Run a quick count query to ensure rows exist.
4. Delete or Reconcile: Use a safe, idempotent delete script that removes all rows matching the job identifier. If the import spanned multiple tables, orchestrate deletions in the correct order to avoid foreign‑key violations.
5. Automate Cleanup: For recurring imports, schedule a nightly job that scans for cancelled jobs older than a threshold and purges associated data.

When writing cleanup scripts, keep the following in mind:

• Always double‑check that the delete criteria match only the imported data.
• Run scripts in a transaction if supported by the database to maintain atomicity.
• Log each deletion step so you can audit the cleanup process.

What to Ask Your Support Team

To tailor the cleanup logic, you may need the following details from your Jira Align instance:

• Does the import job expose a unique importTransactionId that can be used to locate all related rows?
• What database schema does Jira Align use for bulk‑imported entities, and are there foreign‑key constraints that require a specific delete order?

Providing this information to Atlassian support or your internal Jira Align administrator will help you build a reliable cleanup routine.