I’m using Coverity Scan with an OSS project. Most of the issues found are FP’s or by-design, a few are genuine issues. In all cases they’ve been classified as FP, intentional, or fixed. However Coverity is still listing them as “Outstanding Defects” even though there’s no defect there. Is there some magic toggle you have to flip on issues to tell Coverity to stop treating, say, a FP as an outstanding defect?

Currently for FP’s, for example, I’m setting Classification = FP, Severity = Insignificant, Action = Ignore but they’re still showing as outstanding defects even though there’s no defect there.

Edit: Screenshot of the main dashboard.

Screenshot of the “Outstanding defects” tab (note also that the count doesn’t match the dashboard value):

This is sorted by date so it shows that there are issues that were closed over ten years ago which Coverity still marks as outstanding issues.

For reference, if I look at “Issues: Project Scope” I get a bit over 200, so just over half are correctly marked as closed and the rest are (incorrectly) marked as still open. I haven’t been able to identify any pattern in closed vs. (incorrectly) non-closed issues.