Threads for issue reports with sub-locations are not created on GitLab merge requests

[EduardoVaz06]

Bug description
I noticed in some GitLab merge requests that when there are sublocations in the issue, like the one in the printscreen, no threads are created even though the Analysis Details lists it as an issue, and the issue is shown on SonarQube.

Expected behavior
An open thread with the issue, report just like the others.

Screenshots
The print shows 4 issues reported, but only 1 thread opened. The other three issues have sublocations.
(4 issues reported, but only 1 thread opened)

(example of sub-locations)

Software Versions

• SonarQube Version: [v10.6]
• Plugin Version: [1.22.0]

Additional context
Is that an expected behaviour or it's really a bug? This happenning causes some issues to not be resolved before the merge

[mc1arke]

You appear to have duplicated the original screenshot rather than showing a second screenshot with the Gitlab decoration. I'm also not clear on what you mean be 'subissues in the rule', can you provide a bit more detail about what you're seeing in Sonarqube to allow this to be replicated?

[EduardoVaz06]

Sorry! I fixed the print now

With subissues i mean sub-locations, for rules like php:S1142 and php:S5867, for example.