Issue Summary

When a repository import fails in Bitbucket Cloud, users are often unable to view the import logs to diagnose the cause. Instead of seeing the error details, the UI displays an "Access denied:

You do not have permission to view this import log.

This prevents users from understanding why an import failed and how to correct it.

Steps to Reproduce

1. Initiate a repository import in Bitbucket Cloud.

1. If the import fails (e.g., due to a network interruption, timeout, or source availability issue), attempt to view the import status through the email or refresh the import page.

1. Observe the error message displayed on the screen.

Expected Results

If an import fails, the user who initiated the import should be able to access the logs or an error summary to understand the reason for the failure

Actual Results

The UI returns a 403 Forbidden error with the message:

"Access denied: You do not have permission to view this import log."

The repository is often moved to a deleted state, and the user is left with no information on the root cause of the failure.

Workaround

Instead of using the Import tool, users can manually migrate the repository using a mirror clone from a local machine. This bypasses the web-based import process and is more resilient to session interruptions:

1. Create a new, empty repository in Bitbucket Cloud.

1. On a local machine, run:
   git clone --mirror <source_repo_url>

1. Change into the cloned directory:
   cd <repo_name>.git

1. Push the mirrored content to the new Bitbucket repository:
   git push --mirror <bitbucket_repo_url>