Jira Software Project failing migration at kanban board and sprint import at 11%

[Alex P]

I have successfully migratied projects in the past and just recently tried migrating again. I was successfully able to three service desk projects but the software project fails with the following errors:

2023-03-17 22:54:22.699977 ERROR project-import We couldn't import Board 'Backlog'. Reason: 403 Forbidden: "{"errorMessages":["You currently don't have access to perform this operation."],"errors":{}}".

2023-03-17 22:54:23.155228 ERROR project-import We couldn't import Sprint ''. Reason: 403 Forbidden: "{"errorMessages":["You currently don't have access to perform this operation."],"errors":{}}".

This article (https://confluence.atlassian.com/cloudkb/jcma-migration-error-project-import-we-couldn-t-import-sprint-board-sprint-board-name-reason-403-forbidden-1167831742.html) says you must have administer projects permissions, which I do and have tried with multiple users. It keeps failing at 11 % with these errors. I am the owner of the filter and board that it is failing import on and an org and site admin in both on-prem and in the cloud.

Any advice will be much appreciated!

Thanks!

[habib rahman]

Hi @Alex P - My name is Habib - 

The error message you're seeing suggests that the migration process is failing because the user account you're using to perform the migration doesn't have sufficient permissions to access and modify certain components of your Jira Software project, such as the Backlog board and Sprints. To resolve this issue, you'll need to ensure that the user account you're using has the necessary permissions to perform the migration. Here are some steps you can follow:

1. Check the permissions of the user account you're using to perform the migration. Make sure that the user account has the necessary permissions to perform actions like creating and modifying issues, boards, and sprints in Jira Software.
2. If the user account doesn't have the necessary permissions, you'll need to grant those permissions. This can typically be done by assigning the user account to a group that has the necessary permissions or by modifying the user's permissions directly.
3. Once you've confirmed that the user account has the necessary permissions, try the migration again. If the migration still fails, you may need to check the logs for more detailed error messages or consult with Atlassian support for further assistance.

It's also worth noting that Jira Software provides a variety of migration tools and plugins that can simplify the migration process and help you avoid common issues like this one. If you're not already using a migration tool, it may be worth exploring your options to see if there's a tool that can help you streamline the migration process and avoid errors like this one.

I hope this also helps

Habib 

[Alex P]

Habib,

Thanks for your response. I have all of the necessary permissions. Org admin/site admin on both on-prem and cloud, part of the administer projects permissions for both the Administator role and individually added, part of the admin group that is on the project, and individually added as an admin for that project, and even the owner of the board. Also individually added myself to the three sprint permissions for the project (edit, manage, and start/stop sprints).

I am using the Jira migration tool as well. The logs say I 403-access denied for that board, as well as for those sprints.

I also have a ticket with Jira but still waiting for a resolution.

Thanks!

[Oday Rafeh]

Hi @Alex P , It's a very strange error that you getting, and you've already checked the common causes for this error. 

A few additional steps you can try: 

Double-check your permissions:

Ensure that you have "Administer projects" permission in both the source and target instances.
Verify that the user performing the migration is a member of the "jira-administrators" or "jira-software-users" group in both instances.

Check the filter sharing:

Ensure that the filter used by the Kanban board is shared with the necessary groups or project roles in both the source and target instances.
If the filter is not shared, try sharing it with a broader audience (such as "Everyone") temporarily during the migration process.

Inspect board configuration:

Check if the board configuration in the source instance contains any custom settings, such as Quick Filters or Swimlanes, that may be causing issues during the migration.
Temporarily simplify the board configuration in the source instance, if possible, and attempt the migration again.

Review app-related configurations:

If you're using any apps in your Jira instances that may affect boards or sprints, check their configurations and ensure that they are set up correctly for the migration process.

Jira Cloud Migration Assistant (JCMA) version:

Ensure that you're using the latest version of the JCMA, as it may contain important bug fixes or improvements that can resolve migration issues.

Hope this will help in any way 

My regards 

Oday

[Alex P]

Checked permisions and confirmed all are there

Tried changing filter sharing to everyone but still nothing

Board has swimlanes and quick filters, but not sure how this could relate? It isn't too crazy

We do not use any apps on our projects

Thanks though