Team Queries (CMMI)
You can use the team queries that are provided with MSF for CMMI Process Improvement v5.0 to list the requirements, tasks, bugs, and other work items for which you must take action. Each query is designed to find only work items that are defined for the team project from which they are accessed.
You can open these queries from Team Explorer by expanding your team project node, expanding Work Items, and then expanding Team Queries. All team queries list work items that are defined for the team project. Team queries whose query type is Work Items and Direct Links Query or Tree Query may also list linked work items that are defined for another team project.
Note
To access work item queries, you must have the appropriate permissions. For more information, see Organize and Set Permissions on Work Item Queries and Team Foundation Server Permissions.
In this topic
|
Team Queries in Team Explorer .png "Team Queries list in Team Explorer") |
Quick Tips for Managing Work By Using Team Queries
If you are new to Team Foundation and team queries, you can review the following tips for an overview of how you can manage work more effectively by using team queries:
You can find work items that are assigned to you by opening one of the "My" team queries. To open a query, right-click it, and then click Open or View Results.
You can find work items that are neither resolved nor closed by using any of the Active or Open team queries. For example, the Open Work Items query lists all work items, except for shared steps, that are not closed.
You can modify any query by adding criteria to focus on a product area, an iteration, or another field that is defined for the types of work items that you want to find. To modify a query, right-click it, and then click Edit. For more information, see Specify Query Filter Criteria.
You can open any query in Office Excel and Office Project, where you can modify the query and publish your changes to the database for tracking work items. For more information, see Create, Open, and Modify Work Items Using Office Excel.
For more information about how to work with work item queries, see Finding Bugs, Tasks, and Other Work Items.
Finding Work Assigned to You
You can find the work items that are assigned to you by using one of the team queries that the following table describes.
Team Query |
Description |
|---|---|
My Test Cases |
Lists all test cases that are not closed and that are assigned to the team member who is running the query. Test cases are sorted by priority and then ID. |
My Work Items |
Lists all work items, excluding shared steps, that are not closed and that are assigned to the team member who is running the query. Work items are sorted by rank, priority, type, and ID. |
Development and Testing
Team members can use the team queries that are described in the following table to track the status of development and test tasks and active and resolved bugs.
Team Query |
Description |
|---|---|
Active Bugs |
Lists all active bugs and sorts them by rank, priority, and severity. |
Development Tasks |
Lists all tasks whose Discipline is set to Development. Tasks are sorted by ID. |
My Test Cases |
Lists all test cases that are not closed and that are assigned to the team member who is running the query. Test cases are sorted by priority and then ID. |
Open Tasks |
Lists all tasks that are not closed, sorted by rank, priority, and then ID. |
Open Test Cases |
Lists all test cases that are not closed, sorted by priority and then ID. |
Resolved Bugs |
Lists all resolved bugs that are defined for the team project, sorted by rank, priority, and severity. |
Test Tasks |
Lists all tasks whose Discipline is set to Test, sorted by ID. |
Planning and Tracking
Product owners can use the team queries that are described in the following table to track the status of requirements and untriaged work.
Team Query |
Description |
|---|---|
Customer Requirements |
Lists all requirements, sorted by ID, that have been identified as Scenario or Quality of Service work items. |
Product Requirements |
Lists all requirements, sorted by ID, that have been identified as Functional, Operational, Security, Safety, or a Feature. |
Open Requirements |
Lists all requirements that are not closed, sorted by iteration ID, priorty, and then work item ID. |
Open Requirements without Test Cases |
Lists all requirements that are not closed and that do not have a Tested By link to a test case, sorted by work item ID. |
Open Work Items |
Lists all work items except shared steps that are not closed. Work items are sorted by rank, priority, type, and then ID. |
Proposed Work Items |
Lists all proposed work items, sorted by rank, priority, iteration, area, triage, and then work item ID. |
Reviews |
Lists all reviews, sorted by work item ID. |
Untriaged Work Items |
Lists all requirements, tasks, change requests, bugs, and issues that have not been closed or triaged. The Triage field for these work items is set to Pending, More Info, or Info Received. Work items are sorted by state, triage, rank, priority, iteration, and area. |
Work Breakdown |
Lists all requirements that are not closed and their child requirements or tasks. |
Work Items With Summary Values |
Lists all tasks that have child tasks and that contain non-zero values for the Remaining Work or Completed Work fields. This query is designed to find tasks that report work effort that is already accounted for in their child tasks. For the hours to be counted only once, summary tasks should not be assigned any hours. For more information, see Address Inaccuracies Published for Summary Values. |
Change Management
Product owners can use the team queries that are described in the following table to track change requests and dependencies that have been identified between change requests and requirements.
Team Query |
Description |
|---|---|
Change Requests |
Lists all change requests, sorted by ID. |
Open Change Requests with Requirements |
Lists change requests that are not closed and their linked requirements, sorted by ID. Only change requests that are linked to a requirement with a link type of Affects appears in the list. |
Requirements with Open Change Requests |
Lists requirements and the change requests that are not closed and that depend on them, sorted by ID. Only requirements that are linked to a change request with a link type of Affected By are listed. |
Troubleshooting
Product owners can use the team queries that are described in the following table to troubleshoot issues and risks to the product schedule.
Team Query |
Lists |
|---|---|
Blocked Work Items |
Lists all work items where the Blocked field is set to Yes. Only requirements, tasks, bugs, issues, and change requests can be blocked. |
Corrective Action Status |
Lists all tasks whose Task Type is set to Corrective Action. |
Mitigation Actions |
Lists all tasks whose Task Type is set to Mitigation Action. |
Open Issues |
Lists all issues that are not closed. The Issues Workbook references this query. For more information, see Issues Workbook (CMMI). |
Risks |
Lists all risks, sorted by ID. |
Workbook Queries
The following team Office Excel workbooks are supported by the listed team queries:
The Issues workbook uses the Open Issues team query.
The Triage workbook uses the Untriaged Work Items team query.
You can use these workbooks to review open issues and to rank and assign untriaged work items.
Warning
Because these queries support workbooks, if you change these queries, it will affect those workbooks that use them. For more information about workbooks, see Workbooks (CMMI).
See Also
Tasks
Organize and Set Permissions on Work Item Queries
Access Frequently Used or Recently Viewed Work Items, Queries, and Reports