JQL filter using project id doesn't update ids after migrating from another Cloud instance

Issue Summary

Currently, when migrating from one Cloud instance to another, JQL filter using project ids gets broken showing this error message on the filter query:

A value with ID 'XXX' does not exist for the field 'project'.

Steps to Reproduce

1. Create a JQL Query and save it, referencing a project by its id.
2. Check that the filter functions normally, selecting issues from that project.
3. Migrate this project via Cloud-to-Cloud migration.
4. Check the JQL filter in the destination instance, and you will see:

   A value with ID '10100' does not exist for the field 'project'.

Expected Results

The expected behavior here should be this JQL board filter using "project id" still works when migrated to the cloud.

Actual Results

JQL filters are unable to find the projects by their ids.  "Backlog" and "Active Sprints" show no results after migrating and checking the JQL board filter associated we can see the error message.

This happens because the "project id" in the cloud database is different from the original one. On this lab test the original value was "10100" and after migrating the same has changed to "13700".

It is expected that this affects any entity that would be referred to by id in a filter, such as:

• Projects
• Custom Fields - https://jira.atlassian.com/browse/CLOUD-11805
• Sprints - https://jira.atlassian.com/browse/JRACLOUD-83096 

Workarounds

• Change the "project id" to the "project key" on the Source Jira filters before migrating.
  • The JQL editor can be used to find out which entities the IDs refer to. 
• Change the "project id" to the "project key" on the Destination filters as a post-migration step.
  1.   This would recquire knowing the mapping as well as deleting old filters and recreating/reassociating them with necessary content, like boards.
• Change the "project id" to reflect the newer "project id" on the Jira Cloud. The same can be found on Project Settings -> Details.