first of all, as said, please update to the latest version of the plug-in, version 10.28.0.84542, and then see if the issue still appears. I know with a high certainty that it will, but nevertheless.
The dialog appears when the the issue (in Eclipse, a marker) cannot be found, e.g. due to the settings that are both checked on your end:
Show SonarQube markers for open and resolved issues
Show SonarQube markers only for new code
Please try to uncheck the second one, open the file once and then try to open the issue in the IDE from the SonarQube server as before.
If the same dialog pops up and the preferences are shown, check the box again optionally and then hit Apply and Close. A new dialog should be shown if even after applying the new configuration, the issue cannot be found locally.
If it is not shown, then please come back and I can guide you on how to debug this. It would take too long to write it down now without the exact information that I will then ask from you afterwards
PS: That the SonarQube Server webpage says that everything was correct and the switch was successful is only due to the fact that the server received an ack from the IDE plug-in but does not know if the plug-in internally handles it correctly (including manual changes required from the user) - the connection is not kept open. This is correct behavior tho.
Yes I tried your suggestion but message about preferences keeps popping up . Let me know what steps needs to take to debug . Also the version which we have is 11.14 …and you mentioned latest version as 10.28 …is it correct ?
First could you start the IDE, in the SonarQube Console enable all the options, as described HERE (including the IDE-specific traces).
After that, in the SonarQube preferences, change the settings as said above:
Check Show SonarQube markers for open and resolved issues
Uncheck Show SonarQube markers only for new code
After that, select the whole project and from the context menu click Analyze to analyze all files and to find all the possible issues for the local files. The SonarQube Report view should open with all the issues.
After that, in the SonarQube Console clean the current data. You may have to increase the buffer of the Console as the IDE-specific traces can be a lot.
After that, go onto your SonatQube Server and hit Open in IDE for the issue in question, follow the workflow until a dialog pops up again or one is shown saying the issue cannot be found.
Copy the log from the SonarQube Console and paste it here. If you don’t feel confident with sharing that information, you can DM me the logs.
If you have any questions, just let me know