JQL board filter using project id doesn’t bring expected results after migrating via JCMA

Issue Summary

Currently, when using JCMA to migrate a JSW project to the cloud the JQL board filter using project id 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 Scrum project.
2. Go to Backlog -> Board -> Configure.
3. Change the default filter value from "Project Key" to the "Project id".
4. Check that the filter continues to function normally.
5. Migrate this project via JCMA.
6. On the Board filter query setting in Jira Cloud you will find the error:

   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

"Backlog" and "Active Sprints" show no results after migrating and checking the JQL board filter associated we can see the error message, as explained before.

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".

Workarounds

1. Change the "project id" to the "project key" on the Jira Server filters before migrating.
2. Change the "project id" to the "project key" on the Jira Cloud filters as a post-migration step.
3. Change the "project id" to reflect the newer "project id" on the Jira Cloud. The same can be found on Project Settings -> Details.