Report the old issues from previous project version as new issues in current project version

We can get the new issue email from Sonar Qube server, see below example,

Project: MySonarQubeProject
Version: **30**
26 new issues (new debt: 2h 14min)
        Bug: 2    Vulnerability: 0    Code Smell: 24
    Most impacted files
        File1.cs: 12
        File2.cs: 3
        File3.cs: 2
        File4.cs: 1
        File5.cs: 1

More details at: http://....

Project Settings → New Code → Define a specific setting for this project → Specific analysis
I chose Version 1 as the baseline for the New Code.
My questions is that
Some issues in File1.cs were introduced at Version10.
Now I just modified File1.cs at Version30, and not did any changes for the old issue codes. But it reports that the legacy issues (which were from Version10) as new issues for Version30.
I don’t want that legacy issues are took as new issues in Version30. How to resolve this?
By the way, we still take Version1 as baseline for the New Code.

Thanks very much!

Hi Scott,

Welcome to the community!

You seem to have overlooked the topic template, which prompts for information needed to help in most scenarios. Specifically, what version of SonarQube are you using? You can check the page footer if you’re not sure.

Beyond that:

  • Have you analyzed each ‘version’ of the project?
  • For an issue in the email, when you look at it in SonarQube, what shows up as its creation date?
  • Can you share your analysis log?

The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.

This guide will help you find them.