JCMA migration error: "project-import We couldn't import Sprint/Board '<sprint/board name>'. Reason: 403 Forbidden"

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.

Summary

In order to run a migration plan using the Jira Cloud Migration Assistant app, certain permissions are necessary - namely, you need to be an admin in both your Server and the destination Cloud sites (site-admin).

At times, an admin will need to alter their permissions on the Server instance to bypass the 403 Forbidden error described below.

Environment

  • JCMA latest version
  • Jira Server/Data Center 7.6.0 and higher

Error

These import error messages below might surface if you're affected by the lack of proper permissions on Server (the error will happen on the project-import phase of the JCMA plan, on the Cloud site):

2022-09-12 14:39:55.921507 ERROR <project key> project-import We couldn't import Sprint '<sprint name>'. Reason: 403 Forbidden: "{"errorMessages":["You currently don't have access to perform this operation."],"errors":{}}". This caused 569 other items to fail.
2022-09-19 17:56:25.659495 ERROR <project key> project-import We couldn't import Board '<board name>'. Reason: 403 Forbidden: "{"errorMessages":["You currently don't have access to perform this operation."],"errors":{}}".

Possible Root Cause

The potential cause for this error is related to any changes done to the Permission Schemes of the affected projects on Server.

This can cause the user running the JCMA plan to not have the permissions to manage the projects - and thus, the necessary permission to create those entities on the Cloud site.

Solution

If your JCMA plan fails with this error, make sure to:

  • grant the Administer Project permission to the admin user who is running the JCMA plan.
  • remove the affected projects from the Cloud site as they may have been partially migrated - and purge them from the Trash.
  • run a new migration plan for the affected projects.

For reference: Managing project permissions


Last modified on Sep 28, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.