Developer write code and unable to see in sonarqube dashboard in the branch area

Developer write code and unable to see in SonarQube dashboard in the branch area. If developer didn’t write code also its showing more number of issue in branch. Kindly assist us.
After our last production deployment (1/31) it came to our notice that there was a sudden surge in the number of issues shown on the sonar report in the January month.

Numbers shown on Jan 8th

Blocker 12 issues 1h 40min effort SAME
Critical 1,389 issues 92d effort
Major 796 issues 12d effort
Minor 2834 issues 21d effort
Info 59 issues 2h effort

Numbers shown on Jan 31st
Blocker 12 issues 1h 40min effort
Critical 1,382issues 92d effort
Major 1,909issues 17d effort
Minor 3,312issues 26d effort
Info 58 issues 2h effort

When trying to figure out the code components which might have caused this surge, we tried to put on a filter on the issues introduced in Jan month and we did not find any new issues introduced.

There is a considerable difference in the number of Minor and Major issues in master and test_major branches. Also, the issues shown on the minor, major and master branches are not in sync.

we are unable to see code changes in Creation date for last month under branch in sonarqube dash board.

Thanks & Regards,
Sami.

Hi Sami,

It’s not clear to me what you’re asking with this:

But we try to keep it to one topic per thread. Otherwise it can get messy, fast. So I’ll focus instead on

You say this happened after a “production deployment”. I take that to mean a SonarQube upgrade. You don’t say what version you upgraded from, but with each release, at least some of the rules will get smarter. Sometimes that means detecting fewer False Positives. Sometimes it means fewer False Negatives (i.e. more issues are found by the smarter rules).

And the larger the SonarQube version jump, the more pronounced this effect is likely to be.

 
HTH,
Ann