It is not possible to set up automatic assignment of problems in conjunction with Gitlab

SonarQube Server / Community Build
1

SonarQube v9.9.1 , sonar-scanner-cli:4.7.0.2747, gitlab v16.0
I am trying to implement automatic assignment problematic
shallow cloning disabled
authorization in sonar via gitlab

ci:

sonarqube-check:
  stage: analyze
  image:
    name: registry/sonar-scanner-cli:4.7.0.2747
    entrypoint: [""]
  rules:
    - if: $CI_COMMIT_BRANCH =~ /master|dev|DAT\-|feat_|fix_/
      when: always
    - when: manual
  variables:
    SONAR_USER_HOME: "${CI_PROJECT_DIR}/.sonar" # Defines the location of the analysis task cache
    GIT_STRATEGY: clone
    GIT_DEPTH: "0" # Tells git to fetch all the branches of the project, required by the analysis task
  cache:
    key: "${CI_JOB_NAME}"
    paths:
      - .sonar/cache
  tags:
    - docker
  artifacts:
    name: "${CI_JOB_NAME}"
    paths:
      - ${CI_PROJECT_DIR}/.scannerwork/report-task.txt
  script:
    - sonar-scanner -X -Dsonar.qualitygate.wait=true -Dsonar.projectKey=${SONAR_PROJECT_KEY} -Dsonar.go.golangci-lint.reportPaths=report.xml -Dsonar.go.coverage.reportPaths=coverage.out -Dsonar.go.tests.reportPaths=tests-report.json
  allow_failure: true

nevertheless, sonar does not assign problems, either in a new project or in an old project with new errors, what could be the problem?

2

Hey there.

Have the users you want issues to be assigned to logged into SonarQube, and do their SCM accounts match the SCM data for the project (you can find the user’s SCM accounts under the global Administartion > Users > SCM Accounts)