# SonarQube stopped posting decoration to GitLab merge request **URL:** \ **Category:** SonarQube Server / Community Build\ **Tags:** gitlab, sonarqube\ **Created:** [August 18, 2022, 5:25pm UTC](https://community.sonarsource.com/t/sonarqube-stopped-posting-decoration-to-gitlab-merge-request/70052 "2022-08-18T17:25:54Z")\ **Posts on this page:** 5\ **Page:** 2
**Author:** ![jeverett](https://avatars.discourse-cdn.com/v4/letter/j/b5ac83/32.png) [@jeverett](https://community.sonarsource.com/u/jeverett)\ **Post date:** [February 15, 2023, 1:50pm UTC](https://community.sonarsource.com/t/sonarqube-stopped-posting-decoration-to-gitlab-merge-request/70052/27 "2023-02-15T13:50:07Z")
Any update or is this anything I should focus on in the debug logs? ---
**Author:** ![Guillaume\_Peoch](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/guillaume_peoch/32/42321_2.png) [@Guillaume\_Peoch](https://community.sonarsource.com/u/Guillaume_Peoch)\ **Post date:** [February 21, 2023, 11:00am UTC](https://community.sonarsource.com/t/sonarqube-stopped-posting-decoration-to-gitlab-merge-request/70052/28 "2023-02-21T11:00:03Z")
Hello @jeverett , Could you please share with us the `project scanner properties` from the background task on the project where the Merge Requests are failing? Still in the background task, is the analysis considered a `Pull Request` analysis or a `Branch` analysis? Also, are you using GitLab CI? ---
**Author:** ![emrecih](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/emrecih/32/45259_2.png) [@emrecih](https://community.sonarsource.com/u/emrecih)\ **Post date:** [May 18, 2023, 4:28pm UTC](https://community.sonarsource.com/t/sonarqube-stopped-posting-decoration-to-gitlab-merge-request/70052/30 "2023-05-18T16:28:37Z")
Hi, We are experiencing a similar problem. For some projects, sonarqube is sending comment on merge requests, but for some projects there is no post request in the debug logs. I am wondering if any of you found the root cause which can point me in the correct direction. We are using Gitlab CI. Question: is there any configuration in the sonar scanner analysis which might affect this or is it only a configuration on sonarqube server? ---
**Author:** ![emrecih](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/emrecih/32/45259_2.png) [@emrecih](https://community.sonarsource.com/u/emrecih)\ **Post date:** [May 18, 2023, 5:37pm UTC](https://community.sonarsource.com/t/sonarqube-stopped-posting-decoration-to-gitlab-merge-request/70052/31 "2023-05-18T17:37:50Z")
Hi again, I have seen that there was a change on this with versiob 8.1. Here is the information about it: [[SONAR-17711] - Jira](https://sonarsource.atlassian.net/browse/SONAR-17711) Our sonarquber version is 9.3. If i did not misunderstand for this version, this configuration should be done on server side. But I could not find documentation with version 8.1 where this configuration came into picture. So my questions: - why don’t you have documentations for all versions? - what configuration should I do on server side for merge request decoration on server side and how to do it? ---
**Author:** ![emrecih](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/emrecih/32/45259_2.png) [@emrecih](https://community.sonarsource.com/u/emrecih)\ **Post date:** [May 19, 2023, 12:33pm UTC](https://community.sonarsource.com/t/sonarqube-stopped-posting-decoration-to-gitlab-merge-request/70052/32 "2023-05-19T12:33:24Z")
Hi again, I have found our problem and wanted to share here. In the merge request job, I had “sonar.branch.name” parameter and it causes Sonarqube does branch analysis only (if I am not wrong). So it was not sending any merge request comment to Gitlab. After removing this parameter from script, it was able to send the comment on Gitlab. I hope this helps others. [Previous page](https://community.sonarsource.com/t/sonarqube-stopped-posting-decoration-to-gitlab-merge-request/70052.md?page=1)