Prioritize Code Quality findings on change frequency

Release notes

Currently in GitLab there isn't a way to see code with quality issues that's changed frequently. Offering a prioritization mechanism for the Code Quality findings based on change frequency can solve that.

Problem to solve

Provide a way to prioritize the findings of the Code Quality scan based on the code change frequency for that code.

Proposal

Offer the option to prioritize the results of the Code Quality scan based on the change frequency for that code. Code that has code quality issues which is changed more frequent should be identified more easily than code with quality issues that's not changed that frequently. This can help managers get an overview of the code that's not high quality and where investing in addressing issues has a high ROI.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.