Disposition issues on feature branch

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    SonarQube Enterprise Edition V10.5.1 (90531)
  • how is SonarQube deployed: zip, Docker, Helm
    It is deployed as part of the bigbang installation using helm.
  • what are you trying to achieve
    We are trying to inspect code quality, static analysis of code to detect bugs code smells, and code coverage analysis.
  • what have you tried so far to achieve this
    We are seeing that when we disposition an issue on a feature branch, that disposition doesn’t propagate to the main branch. Do we need to enable the SCM/DevOps platform integration to fix this issue? Should the disposition of issues propagate from feature branches to main?

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

3

Hey there.

If you mark an issue on a feature branch as False-Postiive / Won’t fix, and then use Pull Request Analysis before merging that branch to your main branch, the issue disposition should carry over.

You could also choose to only use Pull Request Analysis, which is frequently what our users do (added benefit: incremental analysis speeds up analysis time).