Capturing number of problems identified and solved

Would like to check if there is a way to capture the number of problems identified by SonarQube for IDE during development and the number of problems fixed as a result of Shift Left.

We are promoting the ‘SonarQube for IDE’ usage in the organization. If there is a way to capture the metrics we can sell it easily :slight_smile:

Thanks.

1 Like

Totally agree — having metrics around issues identified and resolved through SonarQube in the IDE would make the Shift Left case much stronger. While SonarQube tracks issues over time, capturing IDE-specific data might need some custom logging or plugin-level reporting. Definitely worth exploring.

1 Like

Hi all,

Sorry, but this isn’t available.

 
Ann

Hi @IamGuna and @benis_froms,

Thanks for raising this - it’s a great point, and I totally see how having clear metrics from SonarQube in the IDE would strengthen the Shift Left narrative within your org.

As @ganncamp mentioned, we don’t currently track issues identified and resolved specifically in the IDE. That said, this ties closely to some broader reporting needs we’re exploring, especially around issue lifecycle and developer interactions, with the goal of better supporting ROI and shift-left adoption cases.

If you’re open to it, I’d love to hear more about what kind of reporting or visibility would be most useful for you when promoting IDE usage. You can book a time with me here: Calendar Booking Link, or just share your thoughts here in the thread!

Best,
Simone
Product Manager for Enterprise Value and Reporting

2 Likes