Changing an issue's status to show how it should be handled
| In this topic: |
Once you've assessed detected issues, the next step is to change their status and add comments, to indicate how they should be handled.
Using statuses such as Not a Problem, Ignore or Defer is a handy way to suppress issues in your results that you don't care about (often in third-party libraries). Note that if you have determined that one or more detected issues are false positives, you should log a ticket with Customer Support.
You can change the status for one issue at a time, for a group of issues, for selected issues, or for an entire list. You need the Change Issue Status permission to change issue status.
Once you change an issue's status to something other than Analyze or Fix, you won't see it again because default filtering options hide all issues in statuses other than Analyze and Fix. You can adjust the list by making another selection in the Searches list or by entering your own search query.
Changing the status for individual issues
In the left pane of the issue details view, select a status from the Status drop-down and add any relevant comments. Typically, if you decide that an issue doesn't need to be fixed, you select either Not a problem to indicate a false positive, or Ignore to indicate an issue that you don't care about (third-party libraries, for example). The status you select should reflect your organization's policy. For the full list of statuses, see Issue statuses.
Changing the status for multiple issues
Typically, you'd edit a single issue at a time if it required some investigation and you were dealing with a short list of them (as described above).
Other times it makes sense to edit many issues at once from the list of issues.
Changing the status for grouped issues
If you have a group of related issues, you can apply a status to the entire group. In the left pane of the issue details view, select a status from the Status drop-down and add any relevant comments. Then, check the Apply to all check box and the status applies across the entire group when you save your changes.
Changing the status for selected issues
For example, you may want to change the status for several issues at once in a particular file. In this case, you'd sort the issues by file in the list, Ctrl-click the issues you want to edit, and click Edit selected at the top of the list.
Changing the status for the whole list
Other times, you may wish to edit hundreds of issues at once, particularly when you're handling many issues in a third-party library and want to set all of them to Ignore. Or, your organization may have decided to establish what we call a baseline, by changing the status for all issues found in the integration build and then addressing only new issues.
To change the status for the whole list of issues:
- Set up a view or use a search query that will list all the issues you wish to manage at once.
- Click Edit all at the top of the list.
- Select a status, add a comment, and click Submit.
Sending a ticket to the bug tracking system
If Klocwork Static Code Analysis has been integrated with your bug tracking system, you can use the button below the Comment pane to create a bug report for this issue in the bug tracker.
In the example, the button is labeled with customized text, Send to Bugzilla, instead of the default value, Create a ticket. You can use whatever text suits your setup.
When you click the button, all the information relating to the issue is sent to the bug tracker, according to the script that controls the integration. Depending on the way the integration is set up, the ID of the bug in the bug tracker system may be displayed as the field BUG ID on the issue details page and in the Issues list.
