Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
JCMA - 1.10.0, JCMA - 1.10.1
-
None
-
Minor
Description
Issue Summary
This is reproducible on Data Center: yes
There are two ways a board or filter can reference a project in its JQL query-
- Project id
- Project key
When the JQL query contains project id(s) instead of project keys, it works fine in server. Whilst in cloud, the same board / filter doesn't function even when the project is present in cloud.
Steps to Reproduce
- Create a project and a board for it. The board should have the project id in its JQL
- Migrate the project. The board should also get migrated to cloud.
Expected Results
Board in cloud functions properly and has the same issues as it has in server.
Actual Results
Board doesn't function in cloud and fails to load the issues saying it cannot find the project.
Workaround
Before performing the migration, go through the boards and filters. And update their JQL queries to not have project id(s). If present, replace those project id(s) with the corresponding project key(s).
Attachments
Issue Links
- duplicates
-
MIG-907 JQL board filter using project id doesn’t bring expected results after migrating via JCMA
- Gathering Interest