You can use the work item queries that are provided with GovDev for TFS 2010 to find the bugs, tasks, and other work items for which you must take action. Each query is designed to find only those 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.
|
|
|---|
|
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
|
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. Each query returns one specific type of work item.
|
Team Query |
Description |
|---|---|
|
My Bugs |
Lists all bugs that are not closed and that are assigned to the team member who is running the query. Bugs are sorted by state, rank, priority, and severity. |
|
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 Tasks |
Lists all tasks that are not closed and that are assigned to the team member who is running the query. Work items are sorted by state, rank, and priority. |
Building
and Maintaining the Backlog
Product owners can use the team queries that are defined in the following table to plan and track requirements and use cases that compose the backlog.
|
Team Query |
Description |
|---|---|
|
Use Case Planning |
Lists all use cases that were not closed in the last 90 days and sorts them by rank. The Use Case Planning workbook uses the Use Case Planning query. For more information, see Use Case Planning Workbook. |
Managing Change
The following table describes the team queries that are listed under the Change Management folder. These queries find requirement and change request work items across the project.
|
Team Query |
Description |
|---|---|
|
Change Requests |
Lists all change requests over the life of the project and sorts them by priority. |
|
Open Change Requests with Requirements |
Lists all active change requests that are linked to requirements. Displays change requests and requirments as direct link list. |
|
Requirements with Open Change Requests |
Lists all requirements with active linked change requests. Displays requirements and change requests as direct link list. |
Planning
and managing an Iteration
The following table describes the team queries that are listed under the Iteration Management, Iteration 1 folder. These queries find work items that are assigned to the specified iteration. As you plan additional iterations, you can modify these queries to specify a different iteration and then save them to the Iteration 2 or Iteration 3 folders.
|
|
|---|
|
The project administrator for each team project defines area and iteration paths for that project so that the team can track progress by those designations. For more information, see Create and Modify Areas and Iterations. |
|
Team Query |
Description |
|---|---|
|
Active Bugs |
Lists all active bugs under the specified iteration and sorts the bugs by rank, priority, and severity. |
|
Active Tasks |
Lists all active tasks under the specified iteration and sorts the tasks by rank and priority. |
|
Bug Triage |
Lists all active bugs under the specified iteration that are not assigned to a team member and sorts the bugs by rank, priority, and severity. The Triage Workbook references this query. For more information, see Triage Workbook. |
|
Completed Tasks |
Lists all tasks that have been closed and sorts them by rank, priority, and severity. |
|
Iteration Backlog |
Lists all use cases and their linked tasks and test cases under the specified iteration path and sorts the use cases by rank and priority. |
|
Iteration Task Backlog |
Lists all use cases and their linked tasks under the specified iteration path and sorts the use cases by rank and priority. |
|
Iteration Test Case Backlog |
Lists all use cases and their linked test cases under the specified iteration path and sorts the use cases by rank and priority. |
|
Open Issues |
Lists all issues under the specified iteration path that are not closed and then sorts the issues by priority. The Issues Workbook references this query. For more information, see Issues Workbook. |
|
Open Test Cases |
Lists all test cases that are not closed under the specified iteration path and sorts them by priority. |
|
Open Use Cases |
Lists all active use cases under the specified iteration path and sorts them by their stack rank. |
|
Resolved Bugs |
Lists all resolved bugs under the specified iteration path and sorts them by rank, priority, and severity. |
|
Use Cases Delivered |
Lists all use cases that are closed via acceptance test under the specified iteration path. |
|
Use Cases without Tasks |
Lists all use casess that do not have a link to at least one task. Use cases are sorted by ID. |
|
Use Cases without Test Cases |
Lists all use casess that do not have a link to at least one test case. Use cases are sorted by ID. |
Managing the Project
The following table describes the team queries that are listed under the Project Management folder. These queries find project management related work items that are assigned to the specified iteration. As you plan additional iterations, you can modify these queries to specify a different iteration and then save them to new iteration folders.
|
|
|---|
|
The project administrator for each team project defines area and iteration paths for that project so that the team can track progress by those designations. For more information, see Create and Modify Areas and Iterations. |
|
Team Query |
Description |
|---|---|
|
Active Tasks |
Lists all active tasks under the specified iteration and sorts the tasks by rank and priority. |
|
All Iterations Backlog |
Lists all use cases and their linked tasks and test cases and sorts the use cases by rank. |
|
All Iterations Task Backlog |
Lists all use cases and their linked tasks and sorts the use cases by rank. |
|
All Iterations Test Case Backlog |
Lists all use cases and their linked test cases and sorts the use cases by rank. |
|
Open Issues |
Lists all issues under the specified iteration path that are not closed and then sorts the issues by priority. The Issues Workbook references this query. For more information, see Issues Workbook. |
|
Open Requirements |
Lists all open requirements and sorts the requirements by priority. |
|
Open Support Tickets |
Lists all open support tickets and sort the the tickets by priority. |
|
Open Test Cases |
Lists all open test cases and sorts the test cases by priority. |
|
Open Use Cases |
Lists all active use cases under the specified iteration path and sorts them by their stack rank. |
|
Requirements Delivered |
Lists all requirements that are closed. |
|
Work Breakdown from Requirements |
Provides a hierarchical listing of all requirements, tasks and test cases suitable for use in a MS Project plan. |
Managing
Testing
The following table describes the team queries that are listed under the Test Management folder. These queries find test related work items that are assigned to the specified iteration. As you plan additional iterations, you can modify these queries to specify a different iteration and then save them to new iteration folders.
|
|
|---|
|
The project administrator for each team project defines area and iteration paths for that project so that the team can track progress by those designations. For more information, see Create and Modify Areas and Iterations. |
|
Team Query |
Description |
|---|---|
|
Active Bugs |
Lists all active bugs under the specified iteration and sorts the bugs by rank, priority, and severity. |
|
Open Test Cases |
Lists all open test cases and sorts the test cases by priority. |
|
Resolved Bugs |
Lists all bugs under the specified iteration path that are resolved and sorts the resolved bugs by rank, priority and severity. |
Finding
Tasks with Summary Values
The Work Items With Summary Valuesteam query, which is located in the Troubleshooting folder, lists all tasks that have child tasks and that contain non-zero values in 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.
Workbook
Queries
The following team Office Excel workbooks are supported by the listed team query:
-
The Use Cae Planning workbook uses the Use Case Planning team query.
-
The Iteration Task Backlog workbook uses the Iteration Task Backlog team query.
-
The Issues workbook uses the Open Issues team query.
-
The Triage workbook uses the Bug Triage team query.
|
|
|---|
|
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 (GovDev). |