All about viewsThink of a view as a way to see exactly what you want to see in your project's defect analysis and reporting. Generally, you don't want to see the entire analysis - you want to see only the defects in the code you're responsible for, or the most important defects, or how many defects have been fixed since the last analysis run. You probably also don't want to see defects in third-party code or test code. You can easily set up multiple views for each of your projects and share them among your team. Note: The 'grouping' keyword is not supported for views.
A view is just a search string, comprised of one or more keywords and values. For example, if you want to view only defects of the highest severity, use this string to create a view: severity:1 Once you set up a view, you can look at both detected issues and reports through that view. In our example, when you go to Issues, you'll see only Severity 1 defects. And if you perform a search, for example for NPD, your search returns results only within the current view -- you'll see only Severity 1 NPD defects. The same holds true for reports: only the data from the current view is included in reports. You can easily switch your view of the project at any time. In our example, if you switch to the default view, you'll now see NPD defects of all severities. Views are project-specific. But since views are created with a simple search string, it's easy to set up the same view in multiple projects. |