Message-ID: <886628237.203.1425222752979.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_202_40556848.1425222752979" ------=_Part_202_40556848.1425222752979 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page describes the actions you can perform on individual issues. Th= ose actions can also be performed on sets of issues in bulk change operations.
To perform review actions on an issue, you must be logged in and have th= e Browse permission on the project the issue is in= (plus the Administer Issues= permission to flag the issue false positive or to change its seve= rity). If you have the correct permissions, you see a row of links added to= the bottom of the issue block.
To start a thread of discussion, use the Comment link.&= nbsp;
Each comment is added to the issue block in a running log. You may edit = or delete your own comments.
To mark an issue as false positive, click on the False Posi= tive link. You must have the Administer Issues permission to perf= orm this action.
Note that false positives are not displayed by default in the Component&= nbsp;viewer. To display them, select False positives&= nbsp;in the drop-down list:
If you tend to mark a lot of issues as false positives, it means that so= me coding rules are not appropriate for your context. So, you can either co= mpletely deactivate them in the = ;quality profile or use issue e= xclusions to narrow the focus of the= rules so they are not used on specific parts (or types of object) of = your application.
Any issue (with a status of Open or Reopened= or Confirmed) can be assigned to a developer by cl= icking on the Assign link.
Because issues are fully integrated with the Notification service, developers can receive email notification= s when issues are assigned to them, changes are made on issues reported by = them, etc.
The severity of any issue can be changed by clicking on the Change severity link. You must have the Administer Issues permission = to perform this action.
Action plans can be created to gro= up issues. Action plans are buckets of issues that you want to group becaus= e they will have a similar timeframe for resolution.
Action plans can be created by pro=
ject administrators from Configuration > Action Plans:
Each issue can then be linked to a= n action plan:
The Action Plans widget lets you track action plan stat= us:
Both the issue counts and the segments of the bar graph are linked to th= e lists of relevant issues.
The change log of an issue can be = displayed by clicking on the title of the rule and then on the Chan= gelog link:
It is possible to link an issue to= an external task manager. To link issues to JIRA for example, you can inst= all the SonarQube JIRA p= lugin.