Since Technical Debt is summation of Efforts of all Code Smells, how is Effort for a particular Issue is calculated?
It varies by rule. You might be interested in the Evaluation of the remediation cost section of the Adding Coding Rules > Coding Rule Guidelines documentation.
It’s not exactly scientific, but it’s meant to give a rough estimate based on the experience of the individual/team developing the rule.
What is the exact file in github source code https://github.com/SonarSource/sonarqube/tree/branch-6.7 which provides this kind of mapping of a potential issue to the remediation effort associated with it based on SQALE and further the remediation cost calculated on it
Thanks for the help.
Can you share some 2-3 repositories you are talking about so we can get better understanding of the mapping of issue to the cost.
A real SonarQube instance is going to be the user friendly option: but here is one example from the sonar-java repository (sorry I don’t have time to find more!)
These mapping files are a part of plugins like sonar-java-plugin-4.15.0.12310.jar
or some other plugin
