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

Improve naming of "on New Code" metrics in Project Measures

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 6.0
    • Fix Version/s: None
    • Component/s: Measures, Web
    • Labels:

      Description

      We are generally using a common naming convention for the metrics that apply to the Leak Period: '... on New Code'.
      But the metrics about issues are named 'New...', and "Lines on New Code" introduced by MMF-295 looks weird as it tries to match the convention.

      Options:

      1. Some metrics really apply on new code such as Line Coverage, Technical Debt Ratio.. but when we are talking about really added or updated lines/conditions, we could use "New...":
        • Coverage:
          • New uncovered lines
          • New uncovered conditionns
          • New lines to cover
        • Duplications:
          • New duplicated lines
          • New duplicated blocks
        • Size:
          • New lines
      2. The wording "New..." is currently used for issues only. We could keep that exception and, as an alternative, simply rename "Lines on New Code" to "Lines of New Code". We would then stay close to our current convention but be more syntactically correct.
      3. (The preferred one at the time being)
        As part of MMF-473, all the differential metrics should always apply to the leak period.
        We could then rename all those metrics from 'New...' and '.. on New Code' to '... on Leak Period Code' or '.. in the Leak'.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              christophe.levis Christophe Levis
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: