Define a work item query in Azure Boards
TFS 2017 | TFS 2015 | TFS 2013
Visual Studio 2019 | Visual Studio 2017 | Visual Studio 2015 | Visual Studio 2013
Work item queries generate lists of work items based on the filter criteria you provide. You can then save and share these managed queries with others. In contrast, semantic searches list work items, but can't be saved or shared.
Create queries from the web portal or from a supported client, such as Visual Studio Team Explorer and Team Explorer Everywhere. You can also define and import a work item query using WIQL syntax and a .wiq file. To support bulk updates or additions, import or export queries using Excel.
If you find that your queries take too long to return results, review the Guidance to create high-performing queries.
In this article you'll learn:
- How to add or create a query
- How to query across projects
- How to group and ungroup query clauses
- How to create a tree of work items or a direct-links query
For quick access to all query tasks, supported operators—such as,
In Group, and
<>(not operator) — based on field data type, and query examples, see Query quick reference.
Choose a query filter
From the Query Editor, exercise the following filter functions. Choose the filter to jump to an article with sample queries. Along with the query filters, you can interactively apply filters to query results.
Along with the filters you use from the Query Editor, you can interactively filter a query result using the Filter function. To learn how, see Interactively filter backlogs, boards, queries, and plans.
- By default, all project members and users with Stakeholder access can view and run all shared queries. You can change the permissions set for a shared query folder or shared query. For details, see Set query permissions.
- To add and save a query under Shared queries, you must be granted Basic access or higher. Also, you must have your Contribute permission set to Allow for the folder you want to add the query to. By default, the Contributors group doesn't have this permission.
Define a flat-list query
You can start a fresh, new query from the Queries tab in the web portal or the Work Items tab in Team Explorer.
Query across or within projects
New queries scope to the current project by default. However, you can create queries to find work items defined within the organization or project collection. All queries that you save, however, are saved under a specific project.
To list work items defined in two or more projects, checkmark Query across projects. For example, the following query finds all features created in all projects within the last 30 days.
With the Query across projects checked, you can add the Team Project field to filter to a select number of projects.
Separate multiple project names with the list separator that corresponds to the regional settings defined for your client computer, for example, a comma (,).
The Team Project field is available only after you check Query across projects. Further, when Query across projects is unchecked, only those fields from those work item types, as defined in the current project, appear in the Field drop-down menu. When Query across projects is checked, all fields from all work item types defined in all projects in the collection appear in the Field drop-down menu.
Define a clause
You create a query by defining one or more clauses. Each clause defines a filter criteria for a single field.
Sample query clause
For a list of available operators based on the field data type, see Query index quick reference.
All clauses you add are added as an And statement. Choose Or to change the grouping. You group clauses to ensure that the clause statements are run in the sequence required.
Choose Add new clause to add another clause at the end of the query, and then choose the Field, Operator, and Value for that clause.
For example, search for all work items assigned to you by specifying the Assigned To field, the equals (=) operator, and the @Me macro, which represents your user identity.
To view the WIQL syntax for a query, and how parenthesis are used to group clauses, install the Marketplace Wiql Editor. This extension supports viewing the WIQL syntax and exporting it to a WIQL file for use in REST API calls. To learn more, see Syntax for the Work Item Query Language (WIQL).
Checklist for how to define a query clause
In the first empty row, under the Field column heading, choose the down arrow to display the list of available fields, and choose an item in the list.
For more information, see Query Fields and Values.
In the same row, under the Operator column heading, choose the down arrow to display the list of available operators, and choose an item in the list.
For more information, see Operators.
In the same row, under the Value column heading, either type a value, or choose the down arrow, and choose an item in the list.
For more information about how to use a macro or variable to specify the current project, user, date, or other selection, see Variables.
To add a clause, choose Add new clause.
You can add a clause to the end of the query, insert a clause after an existing clause (), and remove (), group (), and ungroup () clauses as needed.
Use a work item tree to view hierarchies
Use the Tree of Work Items query to view a multi-tiered, nested list of work items. For example, you can view all backlog items and their linked tasks. Expand (Expand node () or collapse () nodes to focus on different parts of the tree.
You can't construct a query that shows a hierarchical view of Test Plans, Test Suites, and Test Cases. These items aren't linked together using parent-child link types. However, you can create a direct links query that lists test-related work items. Also, you can, view the hierarchy through the Test>Test Plans page.
Define the filter criteria for both parent and child work items. To find linked children, select Match top-level work items first. To find linked parents, select Match linked work items first.
Use direct links to view dependencies
Use the Work items and Direct links query to track work items that depend on other tracked work, such as tasks, bugs, issues, or features. For example, you can view backlog items that depend on other items being implemented or a bug being fixed.
Use the direct links query to track dependencies across teams. The query also helps you manage commitments your team makes. Choose the filter criteria for the top and linked work items. And, select the types of links to filter the dependencies.
Filter your first-tier list of work items by choosing one of these options:
Only return items that have matching links: First-tier work items return, but only if they have links to work items specified by the linked work items filter criteria.
Return all top level items: All first-tier work items return despite the linked work items filter criteria. Second-tier work items that are linked to the first tier return if they match the linked work items filter criteria.
Only return items that do not have matching links: First-tier work items are returned, but only if they don't have links to work items specified by the linked work items filter criteria.
To learn more about each link type, see Linking, traceability, and managing dependencies.
And/Or logical expression
You specify And or Or to create logical expressions of your query clauses. Specify And to find work items that meet the criteria in both the current clause and the previous clause. Specify Or to find work items that meet the criterion in either the current clause or the previous clause.
Add one new clause for each work item field to refine your search criteria. Add clauses to return only the set of work items you want. If you don't receive the results you expect from your query, refine it. You can add, remove, group, or ungroup query clauses to improve your query results.
Group query clauses to operate as a single unit separate from the rest of the query. Grouping clauses is similar to putting parentheses around an expression in a mathematical equation or logic statement. When you group clauses, the AND or OR for the first clause in the group applies to the whole group.
Grouped clauses operate as a single unit separate from the rest of the query. Grouping clauses is similar to putting parentheses around a mathematical equation or logic expression. The And or Or operator for the first clause in the group applies to the whole group.
As the following examples show, the grouped clauses are translated to the corresponding logical expression.
To view the WIQL syntax for a query, install the WIQL query editor extension which will allow you to see the WIQL version of any Query UI entry. This extension allows you to see just how AND/OR grouped clauses are treated.
|Query||Grouped clauses||Logical expression|
These queries return work items that are type Bug and meet the following logical expressions:
- Query 1: AND State=Active OR Assigned to @Me
- Query 2: AND (State=Active OR Assigned to @Me)
- Query 3: OR (State=Active AND Assigned to @Me)
To group one or more clauses, select them and then choose the group clauses icon.
You can also group several grouped clauses. Check the boxes of each clause that's already been grouped. Then, choose the group clauses icon.
If your query results don't return expected results, follow these steps:
- Make sure that each clause is defined as you intended.
- Verify And/Or assignments to each clause. If your results contain more work items than expected, often an Or clause is present instead of an And clause.
- Determine if you need to group or change the grouping of the query clauses and the And/Or assignments of each grouped clause.
- Add more query clauses to refine your query filter criteria.
- Review the options available to specify fields, operators, and values.
Ungroup a clause
That's the basics about defining queries. For an index of query examples, see Query quick reference.