Bulk Update ITSM Tickets (Async)

Update multiple ITSM tickets asynchronously with the same field values.

Creates an async job to process the bulk ticket updates and returns immediately with a job_id. Use GET /jobs/ to poll for job completion and results.

Request:

• ticket_ids: List of 1-50 ticket UUIDs to update
• updates: Fields to update (same for all tickets)
  • status, priority, assigned_user_id, name, description

Response (202 Accepted):

• job_id: UUID to poll for job status and results

Job Status Polling:

• Use GET /jobs/ to check status
• Status flow: QUEUED → RUNNING → SUCCESS/FAILED
• On SUCCESS: all tickets were updated; no per-ticket result data is returned
• On FAILED: job.failure_reason contains a JSON object with per-ticket breakdown:
  • total/succeeded/failed counts
  • results[]: per-ticket entries with success, error, request_index, ticket_id

This follows the vendor-first pattern:

1. Job updates tickets in the vendor system (e.g., JIRA) using bulk APIs
   • Status changes: Bulk transition API (single get_transitions call + bulk_transition_issues)
   • Field updates: Bulk edit API (only for tickets that succeeded status transition)
2. Updates local database for successfully updated tickets

All update fields are optional. Only provided fields will be updated.

Performance: Returns immediately; processing happens asynchronously