1. Context & Background

In large-scale or phased enterprise migrations, teams frequently pre-migrate / preload attachments ahead of the cutover window to minimize downtime. When the final cutover run is executed (migrating issues, history, and project configuration), all attachments for the selected projects have already been transferred to the cloud container, or no new attachments exist.

2. Current Behavior

• During subsequent migration runs where attachments were already migrated, JCMA still displays a running progress bar / spinner showing 0 KB of 0 KB (see attached screenshot).

• This creates ambiguity during time-critical cutovers, leading Migration Support Engineers (MSEs) and customers to wonder whether the attachment stage is hung, actively transferring data, or already finished.

3. Proposed Solution

• Explicit Status Tag & UI Indication:

• • If a project’s attachments were already migrated in a previous plan/run and no delta exists, display a clear label such as Attachments already migrated or Skipped (0 new attachments) instead of a spinning 0 KB of 0 KB bar.

• • Immediately mark the attachment task as complete/skipped.

• Pre-check / Delta Detection:

• • During plan validation or preflight, verify whether all attachment hashes/IDs for the target project already exist in Cloud. If 0 new attachments are found, bypass the upload phase entirely.

• Plan Configuration (Optional):

• • Provide an explicit option or confirmation indicator in the plan creation wizard acknowledging that attachments for the selected project were previously transferred.

4. Impact & Value

• Reduces Cutover Risk & Anxiety: Eliminates confusion around stuck or running 0 KB transfers during high-stakes cutovers.

• Optimizes Cutover Time: Saves pipeline setup and container verification time by immediately bypassing redundant attachment processing.

• Improves Log & Report Clarity: Migration summaries clearly reflect that attachments were skipped due to pre-existing data rather than zero-byte transfers.