Versions Compared

Old Version 1

changes.mady.by.user Antonio Calero

Saved on

compared with

New Version Current

changes.mady.by.user Carlos Sánchez Prieto

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

This page shows you how to configure the integration with SonarCloud. Are you looking for SonarQube on-premise cconfiguration? See ConfigurationSonarQube Connector for Jira Cloud. You can consult here how to configure Sonarqube Connector for Jira Server/Data Center: See Configuration for Jira Server/Data Center

Global Settings Configuration

You can configure a global server to share the configuration on all Jira projects. This is very useful if your Sonar instance is the same for all your Jira projects.

...

There are different 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. 

  • The token type must be USER token type. You can find more information about SonarQube tokens here: https://docs.sonarqube.org/display/SONAR/User+Token

  • SonarCloud Organization: this parameter is needed if you have configured SonarCloud as SonarQube Server URL.

  • Open AI Settings (Experimental) : Configuring this field will automatically add comments to Jira issues created by the application (3 comments max). These comments are suggestions for resolve the problem in code using the OpenAI API. If you dont have a token, you can generate it from here. Additionally, please note that the feature to use OpenAI's suggestions via the plugin is optional and it is disabled by default. Furthermore, you need to have your own OpenAI API key managed entirely by yourself.

image-20240723-091520.pngImage Added

  • Show history charts : you can enable/disable this option if you want to show history measure charts.

  • History date : you can select a date from which you want to obtain de history measures.

  • Group project cards : the number of of individual project cards displayed in the plugin panel.

  • Last analysis date warning : this option will show a warningn for projects with last analysis date befor this configured date in days (90 days by default).

  • Main Panel Screen : you can select which screen do you want to be main screen (Overview, CWE Top 25, OWASP Top 10, OWASP ASVS or ISO 5055).

  • Filter settings : Select which sonarqube issuetypes are displayed in sonarqube issuesbreakdown.

Project Level Configuration

The plugin configuration is quite simple. You can setup your SonarQube settings in your JIRA project settings section:

Image Removed

Image Removed

...

There are different options:

  • SonarQube Server URL: this is server base URL for your SonarQube

    Cloud

    installation

  • Note : the base URL for SonarQube Cloud is https://sonarcloud.io

  • Token: this field is optional. If your SonarQube

    cloud

    instance is not public, then you will need to setup this field with the security token from a SonarQube user. 

  • The token type must be USER token type. You can find more information about SonarQube tokens here: https://docs.sonarqube.org/display/SONAR/User+Token

Visualization settings:

  • Show history charts : Check

    SonarCloud Organization: this parameter is needed if you have configured SonarCloud as SonarQube Server URL.

  • Open AI Settings (Experimental) : Configuring this field will automatically add comments to Jira issues created by the application (3 comments max). These comments are suggestions for resolve the problem in code using the OpenAI API. If you dont have a token, you can generate it from here. Additionally, please note that the feature to use OpenAI's suggestions via the plugin is optional and it is disabled by default. Furthermore, you need to have your own OpenAI API key managed entirely by yourself.

image-20240723-091749.pngImage Added

...

  • Show history charts : you can enable/disable this option if you want to

    display measures

    show history

    charts for each sonarqube project in Sonarqube Connector Panel Report

    measure charts.

  • History date : you can select a date from which you want to obtain de history measures.

  • Group project

    's

    cards :

    Select this option to set

    the number of of individual project cards

    per page that will be

    displayed in

    Sonarqube Connector Panel Report

    the plugin panel.

Filter settings:

  • Show bugs, vulnerabilities or code smells : Check these options if you want to filter sonarqube findings by Bugs, Vulnerabilities or Code Smells.

  • Last analysis date warning : this option will show a warningn for projects with last analysis date befor this configured date in days (90 days by default).

  • Main Panel Screen : you can select which screen do you want to be main screen (Overview, CWE Top 25, OWASP Top 10, OWASP ASVS or ISO 5055).

  • Filter settings : Select which sonarqube issuetypes are displayed in sonarqube issuesbreakdown.

image-20240723-091839.pngImage Added

  • Resource ID: this is the key of the SonarQube resource where you are going to retrieve the quality metrics. You can get this key from your SonarQube project dashboard or your sonar-project analysis parameters (sonarqube project key). 

    • Note:

      since version 1.4 you

      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

      .

  • Tags :This is an optional field. You can get the projects through the tags associated with them in SonarQube/SonarCloud. These tags can be obtained from your project page in SonarQube/SonarCloud or from the analysis properties. You can configure more than one tag by specifying a comma separated list of tags. The results will be aggregated in a single view with all the resources together.

  • Require all tags : enable this option if you want to retrieve the information from all projects that have exactly all configured tags.

  • Custom metrics:  List of custom metric keys to display in the dashboard, you can specify 1 or a list of metric keys separated by commas. For example: blocker_violations, major_violations, classes. Check with your SonarQube administrator to find out the keys to the available metrics.

image-20240723-091914.pngImage Added

Create Jira Issue Settings:

  • Issue type For Bugs:  this is the default issue type to create new Jira issues based on SonarQube Bugs.

  • Issue type For Vulnerabilities:  this is the default issue type to create new Jira issues based on SonarQube Vulnerabilities.

  • Issue type For Code Smells: this is the default issue type to create new Jira issues based on SonarQube Code Smells.

  • Issue type For Hotspots: this is the default issue type to create new Jira issues based on SonarQube Security Hotspots

    .

Global Settings Configuration

Image Removed

You can configure a global server to share the configuration on all Jira projects. This is very useful if your Sonar instance is the same for all your Jira projects.

Connection settings:

  • SonarQube Server URL: this is server base URL for your 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

Visualization settings:

  • Show history charts : Check this option if you want to display measures history charts for each sonarqube project in Sonarqube Connector Panel Report.
  • Group project's cards : Select this option to set number of project cards per page that will be displayed in Sonarqube Connector Panel Report.

Filter settings:

  • Show bugs, vulnerabilities or code smells : Check these options if you want to filter sonarqube findings by Bugs, Vulnerabilities or Code Smells

    .