Issue Summary

The Bulk Move API (POST /rest/api/3/bulk/issues/move) returns 201 and successfully enqueues the BulkEditTaskRunner, but the async task fails with a generic error when the issue's description field contains large rich text content (exceeding the 1MB text content limit enforced by the Issue Service). This primarily affects email-originated JSM issues, where email threads accumulate significant content in the description. Manual UI move works for the same issues.

Steps to Reproduce

1. Have a JSM project with an email channel configured 

1. Receive an issue via email that generates a large description (email thread content exceeding 1MB)

1. Send a POST request to /rest/api/3/bulk/issues/move with a valid payload to move the issue to another project

1. API returns 201 with a taskId

1. Poll the task status

Expected Results

The async task completes successfully and the issue is moved to the target project.

Actual Results

The async task returns FAILED with: "Error while performing bulk operation on issues. Please refer to Jira logs for more details." No detailed error is surfaced. The issue remains in the source project.

Note: Manual UI move succeeds for the same issue. The 1MB content limit is only enforced in the Bulk Move API path.
 
 BulkEditTaskRunner enqueues successfully but fails silently during execution.No ERROR-level logs are propagated — the async task does not carry the original trace ID to the background thread.

Workaround

Currently there is no known viable workaround for this behavior. Trimming the rich text content in the description field before moving would technically resolve the issue, but is not feasible for automated workflows where email-originated issues naturally contain large email thread content. A workaround will be added here when available.