Message-ID: <294289494.27105.1417121954726.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_27104_1463020292.1417121954726" ------=_Part_27104_1463020292.1417121954726 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This plugin will automatically assign new issues raised in the current a=
nalysis to the SCM author responsible
for the violation.
If the author is not registered in SonarQube the issue can be assigned t=
o a configurable default assignee.
The plugin can handle scenar= ios where the violator is not the original author of the code in which
the issue is raised, but rather the last committer. For example, in metric= s where the length of a
method has exceeded the maximum threshold. In = this case the issue will be assigned to the last committer.
The plugin can be installed via the Update Center.
Configure the plugin as described below and run the SonarQube analysis a= s normal.
NOTE: If you wish to avoid mass issue assignments = on first-time analysis or when rule changes are introduced, disable the plu= gin during the initial analysis and re-enable it for subsequent analyses.= p>
For Git users, the SCM author is an email address. The plugin can map th=
is email address to a Sonar user,
provided the email address i= s the same for the SCM and SonarQube accounts.
Configure this value to be a valid SonarQube login of a user to whom iss= ues will be assigned if the plugin cannot determine the SonarQube user who = is responsible for an issue. An example of this would be an SCM autho= r who has left your organization and no longer has an account in SonarQube.=
The plugin is disabled by default. It can be enabled or disabled i= n either the global or project settings.
Configure this value to be a valid SonarQube login of a user to whom all= issues will be assigned regardless of the SCM author. Useful to avoi= d issues being assigned and notifications being sent out to unsuspecting So= narQube users in testing scenarios.
Assign issue to the last committer= of the file, rather than the author as determined by the SCM metrics.
Assign blameless issues to the last committer of the file. Blameless is= sues are issues that don't have an associated line number and therefore can= not be resolved to a particular commit. For example: squid:S00104 'Files sh= ould not have too many lines'
Extract the SonarQube username fr= om the SCM username associated with an issue using a given regular expressi= on.
Only assign issues introduced aft= er this date. Use the format dd/MM/yyyy.
Only assign new issues raised in = the current analysis. Set to false to assign all qualified unassigned issue= s.
Only assign issues with a severity equal to or greater than a configur= able value.
Notifications can now be sent when= an issue is assigned. In the top-right corner of the GUI, go to <= username> -> My profile -> Overall notifications. Tick 'New = issues assigned to me (batch)' to receive a single notification of all issu= es assigned to you during the latest analysis.
Notification content is also confi= gurable. See the options on the plugin settings page.