Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.6
-
Fix Version/s: 1.12
-
Component/s: Source code viewer
-
Labels:None
-
Number of attachments :
Description
When looking at the violations annotated in the source code, it would be nice to know what plugin triggered that violation. This is useful, for example, because the web contains more information about a particular violation than is included in the description presented in Sonar. Knowing what tool found that violation makes it much easier to locate external information about that particular violation.
Issue Links
| This issue is duplicated by: | ||||
| SONAR-1204 | Show name of the violation reporting tool |
|
|
|
| This issue relates to: | ||||
| SONAR-627 | Manage 5 rule priority levels and associate a weight to each level |
|
|
|
| SONAR-1176 | Add the formal ID of rules in the rule's description |
|
|
|
| This issue is related to: | ||||
| SONAR-61 | Link to rule description from a violation displayed in the resource viewer |
|
|
|
Plugin name and rule key have been added as tooltips on the rule name. A popup opens the full rule description in a new window.