Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-3647

The "added" violation tracking mechanism must be based on exactly the same dates used by the mechanism in charge to compute variations

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0
    • Component/s: None
    • Labels:
      None

      Description

      Here is an example where the two mechanisms are desynchronized :

      • Analyse a project A for the first time (let's say that this project contains 5 violations and 2'000 loc)
      • Create 2 new violations and 200 new loc
      • Analyse project A
        • You get a total of 7 violations and 2'200 loc
        • And +2 violations added since last analysis and + 200 loc -> OK
        • But +7 violations added during past 5 days and + 200 loc -> KO

      Either we should get (+2 and +200) or (+7 and +2'200)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              henryju OLD - Julien HENRY
              Reporter:
              freddy.mallet Freddy Mallet (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved: