Message-ID: <238003472.6321.1406374116705.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6320_1604589614.1406374116705" ------=_Part_6320_1604589614.1406374116705 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. The out-of-th= e-box SonarQube notification framework will then automatically notify the a= ssignee,
If the author is not registered in SonarQube the issue will be assigned =
to a configurable default assignee.
The plugin can handle scena= rios 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 metri= cs 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 is still under vote, so you need to build it yourself:
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.
Set to true if you want to always = assign to the defect author, set to false if you want to assign to the last= committer on the file if they are different from the author.
Any defects introduced or updated after this date are auto assigned, an= d any defects before will be ignored. Use the format dd/MM/yyyy.
Use to identify an email address = embedded into an SCM username. For example, a Git username such as: Gi= tUser<email@example.com>.