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

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 75 Next »

Compatibility Matrix

Plugin

0.1

0.2

0.2.1

0.3

1.01.1

Jira 3.x

(tick)

only 3.13 (tick)

(tick)

(tick)

(tick)

(tick)

Jira 4.x

(minus)

(plus)

(tick)

(tick)

(tick)

(tick)

Jira 5.x

(question)

(question)

(question)

(tick)

(tick)

(tick)

Description / Features

This plugin connects Sonar to Altassian JIRA in various ways.

Widget "JIRA Issues"

Sonar 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 Sonar review to a JIRA ticket

This feature allows you to create a review (on a violation) that will generate a JIRA ticket on your configured JIRA instance.

When logged in, you should find the "Link to JIRA" action available on any violation:

You can enter any comment and after you press "Link to JIRA", a new review comment is added on the violation: you can see the link to the newly-created JIRA ticket.

And the corresponding JIRA look like:

Installation

  1. Install the JIRA plugin through the Update Center or download it into the SONAR_HOME/extensions/plugins directory
  2. Restart the Sonar server

Usage

Mandatory Properties

At project or global level go to Settings > JIRA and set the sonar.jira.urlsonar.jira.login.secured and sonar.jira.password.secured properties.

Security note for Sonar 3.4+

Icon

For the *.secured properties to be read during the project analysis, it is necessary to set the 'sonar.login' and 'sonar.password' properties to the credentials of a user that is:

  • System administrator
  • And project administrator on the project that is being analyzed
Example:
sonar-runner -Dsonar.login=admin -Dsonar.password=admin

To Display Data on the JIRA Issues Widget

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

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

To Create JIRA Issues

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

Note that you can also configure the issue type, the component, the priorities. Browse the JIRA setting page on the web interface for a complete list.

Connecting to JIRA through HTTPS

Icon

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

FAQ

  • Q: I see the following warning in Sonar 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 Sonar does not populate these fields then issue creation fails. How can I make it work?
  • A: The sonar.jira.issue.component.id 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.

Change Log

Loading

Release 1.1 (5 issues)

 

Loading

Release 1.0 (7 issues)

 

Loading

Release 0.3 (1 issues)

 

Loading

Release 0.2.1 (3 issues)

 

Loading

Release 0.2 (5 issues)

 

Loading

Release 0.1 (3 issues)

  • No labels