When SonarQube creates an issue, it automatically assigns it to the person who wrote the respective code, presumably to alert that person that they should fix the issue.
In my company however, we do not work like this. We have regular pair programming sessions where a bunch of SonarQube issues are discussed and fixed, but we never pay attention to who wrote the code. To me, seeing automatically populated assignee fields feels like blaming the individual developers.
I therefore propose a feature that allows disabling this automatic assignment of issues (in SonarCloud: on organization level).