Programming language you’re coding in: Java (IntelliJ)
Is connected mode used: Yes
Connected to SonarCloud or SonarQube (and which version): unknown
When right clicking a code smell and selecting “Mark issue as…”, no options appear for the reason, only a text box for an optional comment. Note, this line item does not have the “Sonar” icon to the far left.
It’s worth noting that there was a different code smell that did have the “Sonar” icon and I was able to successfully resolve that one.
I’m pretty sure you can only mark issues as accepted/false-positive if the issue exists on the SonarQube server. A new issue that only exists in the IDE (for now), can’t be marked.
I’m not 100% sure of the behavior, though, and we could probably do a better explaining that in the UI if so (why would I be able to type in a comment if I can’t mark an issue?). I’ll flag this for review.
Turns out I’m not quite up-to-date. Quoting a developer:
You can mark issues not yet detected on the server; on the following analysis, they will be automatically resolved. There’s an issue in his case, we are supposed to retrieve the list of statuses from the server but apparently it’s empty due to a problem.
I think it would be helpful for you to provide the Verbose logs from IntelliJ in the context of the file where you face this issue.
I there a way to securly upload this to you? As there is a wall of data in which I cannot see if there is sensitive data present or not.
(i.e. I did the help → collect logs trick, if you want different please let me know).
For your information, I was able to reproduce the issue. While the reason nothing is shown might be valid (in my case, I lacked permissions with my token), we should still show a warning and not open the dialog. I have created this bug ticket that I will tackle for our next release.
