I've merged two Jira cloud instances by going from cloud to server with the source, and merging to the target using the jira cloud migration app. The source and target both have zephyr app data, which I'm migrating using Zephyr REST API calls. The problem I'm having is when I try to create a test cycle on the target cloud site I get the error:
API Error: {"errorType":"ERROR","clientMessage":"projectId field value is null or 10,006 is not valid.","errorCode":126}
The project I'm trying to create a cycle on is one which has been migrated using the cloud migration app, and the project ID is indeed 10006, from both the url in project settings and from using a REST API call to Jira. The ID which is being passed to the API call is also definitely an integer and not null, or a string with the , inside.
I know there is no issue with access, the project configuration or the REST API call as I can both create a new cycle using the API call to other projects in the target which were present before the migration/merge, and also to the project whose new ID is 10006 on the source instance (rather than on the target instance).
The only explanation I can think of is that the cloud migration app has failed regarding setting the database or access to the database? I should note also that the atlassian project addons have permission to everything in the permission scheme, so they shouldn't have an issue seeing the project. This is also backed up by the fact that the API call finds the other project (which was already present on the target instance) to create a cycle fine.
I seem to have found the solution. Zephyr requires a project metadata re-index following the cloud migration, after which the error disappears and the valid project ID is correctly interpreted or found as valid.
The re-index is performed by going to COG/Settings > Apps > General configuration (under Zephyr for Jira cloud) and re-indexing.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.