Won't fix issues report again

[Benjamin Liu]

Hi,

Recently, Our sonar server always auto close won't fix issues, and then report them again as open issues. I checked the related files, all of them were not changed.

I'm not sure why this kind of issues happened. Are there any other reasons will result this issue or how we could ignore this issue?

SonarQube Version: 5.6.1

Thanks,

Benjamin

[Duarte Meneses]

Hi,

We are not aware of any problems like that. If a file is unchanged between analysis, SonarQube should be able to match the issues and reuse the existing open issues.

Do the new open issues have the exact same location as the closed ones (same file key, same line)? Do you have a simple reproducer of that behavior? 

[benjami...@gmail.com]

Hi Duarte,

The file did not change, the new open issues have the exact same location as the closed ones. And we cannot always reproduce it. It's a sometimes issue.

And I found, the origin issue has been auto closed(from won't fix to fixed, please check the snapshot) by Sonar. Here is the related post: https://groups.google.com/forum/#!topic/sonarqube/p2JR3_DB5YM

Thanks,

Benjamin

[Duarte Meneses]

Hi,

SonarQube will close an issue if it's no longer found in one analysis. Since the issue is gone from the source code, it's not expected for it to appear again. If in a subsequent analysis the issue appears again, you will have a new open issue.

This is different from issues that you mark as resolved (won't fix, false positive or fixed), in which case the issue is still found by the analyzers, but SonarQube will ignore match it with the issue that was marked as resolved, and ignore it. 

Note that if you mark it as "fixed", it is expected that it is reopened if the issue is still found to be in the code.

Your other post is confusing. You mentioned:

we change its status to CLOSED and resolution to FIXED, but recently a same issue on same file is reported again by sonar.
We didn't change the file recently.

How did you manually change an issue to closed? And if the file is unchanged, it's natural that it will be back in the next analysis.

In the picture that you showed, it looks like the issue was no longer present in the code when the analysis was done on July 25th, so SonarQube closed the issue. 

Does the new issues appear in the same analysis where the issue at the same location is closed?

--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/tNeypY8GCJQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/c4313304-e451-453d-aa68-4d05cfae6750%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Duarte Meneses | SonarSource

Software Engineer

http://sonarsource.com

Are you using SonarLint in your IDE?