Skip to content

SonarQube Frequently Asked Questions

Q: How do I get permissions on SonarQube? A: SonarQube permissions are DL-based, to receive permissions on specific projects you will need to be added to the corresponding team or admin DL.

Q: How often is the SonarQube server upgraded? A: Upgrades to SonarQube are done on a LTS to LTS (Long-term support) basis or if a desired feature or bugfix has been implemented in the latest version.

Q: How to get a portfolio made? A: Portfolios are made per project (i.e. CareLink projects have their own projects). Portfolio requests can be made through a support ticket with Team Energizers.

Q: How to request the definition of a rule to be modified? A: It is best practice to minimize the number of changes done to pre-existing rules, but if deemed necessary a request for the change can be made through a support ticket with Team Energizers.

Following this, a notice will be sent to the SonarQube portfolio managers Teams channel to voice and address any concerns. Once all and if-any concerns are addressed then forum will be open up to the whole of SonarQube userbase Teams channel. If there are no concerns then the rule change will be implemented.

Q: Can we customize the warning message displayed to the developer? A: There are no settings available to change the message of the pop-up when resolving an issue as Won't Fix or False Positive.

Q: If issue is fixed or won't fix, is there a history for how many times? A: Each issue has an associated change log (accessible by clicking on the date of the issue's creation), which will remain as long as the issue itself is not cleared by the Housekeeping policies used by your SonarQube instance. For example:

Q: Can we make the comment field required if they select won't fix? A: While we prompt for a comment when an issue is resolved with any state other than Fixed, it is not required, and cannot be forced to require a comment.

Q: SonarQube is not excluding files when I pass in the sonar.exclusions parameters? A: Verify that your paths are correct or provide a full path to the files. Also when using sonar.inclusions or sonar.exclusions, maintain that the parameters are not colliding.