Uploaded image for project: 'Product Roadmaps'
  1. Product Roadmaps
  2. MMF-1059

Impossible to investigate why new debt can be greater than zero while there is no new code smell

    XMLWordPrintable

    Details

    • Type: MMF
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Do
    • Labels:

      Description

      The initial problem was as follows

      • Create a Sonar profile with only "Insufficient branch coverage" rule
      • Analyse a project that violates this rule on 1 file
        • On the project home page, you see 1 issue
      • In the uncovered branches of this file, add many other branches that won't be covered as well
        • => this will increase the "effort to fix" for this issue
      • Re-analyse the project
        • On the leak period, you still see that there's new debt but no new code smell
        • And if you click on the new debt, you end up on an empty "Issues" page

      The behavior changed with SONAR-9534, which changed the calculation of New Debt to include only debt from New Issues, which is inaccurate for the case described above.

      In this particular case,

      • issue changelog entries should be backdated to avoid raising "new" debt on old issues when rule metadata changes (e.g. parameter value is decreased.)
      • issue search should allow you to search for an issue with technical debt changes after a given date (the beginning of the leak period), which would mean that the change log of every issue should be checked

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              fabrice.bellingard Fabrice Bellingard
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: