The resolution/matching/binding between GitHub projects and SonarQube project is based on GH fullName field, matching exactly the SonarQube key.
The issue with this approach is that if the SonarQube key is updated, the binding would not be recognized anymore. The PR decoration will still work, though.
One the other side, for BBS, we decided to rely on the project_alm_settings. projectKey field to match the ALM project key. That implementation allows SQ projects to be renamed without breaking the binding. And this specific column is exactly made for this purpose: store the ALM project key, regardless of SQ project key.
=> the matching algorithm needs to be changed to rely on project_alm_settings.projectKey instead of GH fullName.
While testing the proposed solution for this bug, we found another bug: projects that had been imported from GH, that had then been unbinded (as the GH configuration was removed) were still appearing as imported. The new matching algorithm should fix that issue as well.