Full documentation for SonarQube has moved to a new location: http://docs.sonarqube.org/display/SONAR

Versions Compared

Key

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

...

This plugin connects SonarQube TM to Altassian JIRA in various ways.

Widget JIRA Issues

SonarQube TM retrieves the number of issues associated to a project from JIRA. It then reports on the total number of issues and distribution by priority.

Link a SonarQube

...

issue to a JIRA ticket

This feature allows you to link a SonarQubeTM issue SonarQubeissue to a JIRA issue. It will create a new JIRA ticket.

...

  1. Install the plugin through the Update Center or download it into the SONARQUBE_HOME/extensions/plugins directory
  2. Restart the SonarQube TM server

Usage

Mandatory Properties

...

  1. Log in to your JIRA instance and create a filter. Mark it as favorite. You can also share this filter with your team in order to allow usage of URL for issues in SonarQubeTM.

  2. And finally specify the sonar.jira.url.param property for project or module: this is the name of an issue filter that you have previously created on JIRA (check JIRA documentation to know more about issue filters).

...

Set the sonar.jira.project.key property that is the key of the JIRA project on which this SonarQube TM plugin will generate tickets

...

Note
titleConnecting to JIRA through HTTPS

If you must connect to your JIRA instance through HTTPS, and if a certificate is required for this connection, then you must import the certificate into the CA store of the JRE that runs SonarQubeTM.

FAQ

  • Q: I see the following warning in SonarQube TM logs when using the JIRA plugin:

    [WARN] [18:32:24.426] Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled.
  • A: This is a message from the Axis SOAP client we are using to talk to your JIRA. You can safely ignore this message. Attachment support is not used anyway.

...

  • Q: I have configured my JIRA instance so that some fields are mandatory. Because SonarQube TM does not populate these fields then issue creation fails. How can I make it work?
  • A: The sonar.jira.issue.component.id property can be defined at project level. For other fields the suggested workaround is to create a new issue type in JIRA (for exemple "Quality issue") and set the sonar.jira.issue.type.id property accordingly.

...