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.

...

• 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).

Image Added

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

• Enable Plugin for projects types : If you only want to see the SonarQube Connector for Jira in some type of project, such as Jira Software project types, it is possible from the Global settings.

Project Level Configuration

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

...

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

...

• 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).

Image Added

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

Image 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). 

...

If your SonarQube instance is using HTTPS then you may need to import your SSL certificate into your JIRA installation using keytool or any other similar tools.

• • Note: you can setup more than one resource/project key by providing a comma separated list of resource keys.

• 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 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.