A grouped issue is one that contains similar issues. For example, multiple 'Array index out of bounds' errors are detected on the same array; this is probably an off-by-one issue that can be fixed by adjusting the array size or the accessors.
Previously a grouped issue was reported as a single issue where the issue details were constructed from the first instance found with a message that stated which lines the issues could be found on. An issue is created for each violation and assigned to a group.
You can use Klocwork Static Code Analysis to display both grouped and ungrouped issues. By default, Static Code Analysis will display groups in issue-list and reports. For example, if foo.c has a group of 5 ABV errors; the issue list and reports display this group as a single issue by default. When grouping is turned off, the issue list and reports will show results for expanded groups. In this case, if foo.c has a group of 5 ABV errors; issue list and reports will display this group as 5 issues.
When grouping is on, the issue list displays group IDs. When it is off, issue IDs are displayed. For example, say an issue group with ID 11 contains 3 issues 57, 58 and 59. If grouping is on (the default), the issue list displays one row with ID 11. If grouping is turned off, the issue list displays 3 rows with IDs 57, 58 and 59. This is represented in the issue details under ID as 'groupID.issueID'. For example:
In the issue list, you can turn issue grouping on or off by using the 'grouping' search keyword. Also, most reports now have a 'group issues' configuration option (on by default) that is accessible in the report editor.
By default, desktop issues are shown with grouping off while server issues are shown with grouping on. If you want server issues for your project to persistently show issues with grouping off, you can change the default setting by using the set-project-property command. For more information, see Kwadmin.