Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The plugin configuration is quite simple.


There are five options:

  • SonarQube Server URL: this is server base URL for your SonarQube installation
  • Token: this field is optional. If your SonarQube instance is not public, then you will need to setup this field with the security token from a SonarQube user. You can find more information about SonarQube tokens here: https://docs.sonarqube.org/display/SONAR/User+Token
  • Authors: List of authors, you can specify 1 or a list of authors (SonarQube login, SonarQube email or SCM accounts) separated by commas. For example: developer@gmail.com, developer, developer@github.com
    • Note: On Jira Server/DataCenter this field is optional. If you leave field empty, we use your Jira login and email.
  • Resource Key: This is the key of the SonarQube resource where you are going to retrieve the Issues. You can get this key from your SonarQube project dashboard or your sonar-project analysis parameters.
    • Note:
      • You can setup more than one resource/project key by providing a comma separated list of resource keys. Measures will be aggregated into a unique view of all the projects together. See section linking multiple projects to Jira.
      • This field is optional. If you leave field empty, we retrieve all SonarQube Issues.
  • Repository Branch: This optional field is used only if you configure 1 project. If you leave field empty, we use main branch
  • No labels