Renamed private bitbucket repository name, now project doesn't appear and can't set it up again

Template for a good new topic, formatted with Markdown:

  • ALM used (GitHub, Bitbucket Cloud, Azure DevOps)

Bitbucket Cloud

  • CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI

Circle CI

  • Scanner command used when applicable (private details masked)


  • Languages of the repository


  • Only if the SonarCloud project is public, the URL
    • And if you need help with pull request decoration, then the URL to the PR too
  • Error observed (wrap logs/code around with triple quotes ``` for proper formatting)

We have a repository that we renamed in bitbucket cloud. It does not show up in the list of projects we have set up in Sonarcloud, but when we go to Analyze New Project, Sonarcloud says it is already set up.

We need to “un” set this up so we can start over from scratch, maybe?

Set up new project:

Monosnap Analyze projects 2023-04-19 07-51-44

Search for project:

  • Steps to reproduce
  • Go to Analyze New Project. The project is there and says has been already set up.
  • but go to list of projects, the project can’t be found.
  • Potential workaround


Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

We resolved this. We went to the URL directly using the old repo name (e.g. SonarCloud), were able to delete it there, and then we could set up the renamed repo as a new sonarcloud project.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.