Issue Summary

When a Jira Cloud Migration Assistant (JCMA) plan includes both projects and apps, the app migration only starts once every project finishes. If even one project fails or times out, the apps never run and the plan ends as Timed out or Failed.

Steps to Reproduce

1. Run the project +apps migration using JCMA .
2. The projects migrate but overall migration is timed out or projects have failed along with migration timedout.
3. Apps migration do not trigger.

Expected Results

• Projects that migrated successfully are marked Complete, and only the failed or timed-out project is marked Failed or Timed out.
• The app migration still runs for all projects that migrated successfully.
• App data for those projects is available on the Cloud site.
• The plan shows clearly which projects failed and gives a supported way to:
  • retry only the failed projects, with their app data
  • retry only the app migration, without migrating projects again
•  The admin can finish the migration without cleaning up the Cloud site or redoing projects that already succeeded.

Actual Results

• One project failing or timing out blocks the whole plan, which ends with status Timed out or Failed.
• The app migration never starts, even though almost every project migrated successfully 

Workaround

• Migrate the failed projects, plus the apps, in a separate plan. Check with the app vendor that the app data comes through correctly.
•  Or, clean up the Cloud site (running an attachment preload first to save time) and rerun the full migration.

Contact Atlassian Support and we can trigger Ready State Apps from backend.