<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=586471) </details> <!--IssueSummary end--> ## Summary **Duo generated bug issue** When a project import fails after partial data has been successfully imported, no error alert is displayed to users. The import state is marked as failed in the database, but users browsing the project see no indication of the failure. For example, a user imported a project into Gitlab.com where `Gitlab::BitbucketServerImport::Importers::PullRequestNoteImporter` processed hundreds of thousands of items, but at some point they started failing with `Unable to parse the server response as JSON` which originates from `check_errors!` [here](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/bitbucket_server/connection.rb#L78-91). If you look at the `/import` endpoint on that project you can see it failed, but can navigate to the project just fine: ```json "created_at": "2026-01-13T14:41:43.673Z", "import_status": "failed", "import_type": "bitbucket_server", "correlation_id": "9bd5a7f4b56c9035-IAD", "failed_relations": [], "import_error": "Unable to parse the server response as JSON", "stats": null } ``` ## Steps to reproduce 1. Start an import of a project (e.g., from Bitbucket Server) 2. Allow the import to progress and create data (repository, issues, pull requests, etc.) 3. Trigger a failure condition during import (e.g., API errors, network issues, rate limiting) 4. Navigate to the imported project ## Expected behavior A clear error alert should be displayed indicating that the import failed and may be incomplete. ## Actual behavior No error alert is displayed. The project appears to have imported successfully, even though the import state is marked as failed. ## Root cause The import failure alert in `app/views/projects/_importing_alert.haml` only displays when the repository does not exist: ```haml - show_failure_alert = project.import_failed? && !project.repository.exists? && can?(current_user, :read_import_error, project) ``` When the repository exists, the alert is hidden. ## Proposed solution The failure alert should display whenever the import has failed, regardless of whether the repository exists. If partial data imports are acceptable, we should clarify that with the end user on why. This ensures users are always informed of import failures, even when partial data has been imported. ## Environment - GitLab.com **18.9.0-pre** [<small>59df4f4a562</small>](https://gitlab.com/gitlab-org/gitlab/-/commits/59df4f4a562)