wiql-queries
Build and execute WIQL (Work Item Query Language) queries for Azure DevOps. Use when the user wants to query work items, find bugs, list tasks, search by assignee, filter by state, find items in a sprint, or build custom work item queries. Use when user mentions "query", "find work items", "list bugs", "my tasks", "assigned to", "in sprint", or "WIQL".
What this skill does
# WIQL Query Reference (Verified) ## CRITICAL LIMITATIONS - READ FIRST 1. **NO TOP CLAUSE** - WIQL does NOT support `SELECT TOP N` like SQL Server. Limit results with shell: ```bash az boards query --wiql "..." -o table | head -10 ``` 2. **Use explicit project name** - The `@project` macro is unreliable in CLI: ```sql -- UNRELIABLE: WHERE [System.TeamProject] = @project -- RELIABLE: WHERE [System.TeamProject] = 'YourProjectName' ``` 3. **Only flat queries supported** - The CLI only supports flat queries, not tree/hierarchical queries. 4. **NO LIKE OPERATOR** - WIQL does NOT support SQL-style LIKE patterns. Use CONTAINS instead: ```sql -- DOES NOT WORK: WHERE [System.Title] LIKE '%keyword%' -- USE THIS INSTEAD: WHERE [System.Title] CONTAINS 'keyword' ``` 5. **CANNOT ORDER BY System.Parent** - Sorting by parent ID is not supported: ```sql -- DOES NOT WORK: ORDER BY [System.Parent] -- WORKAROUND: Filter by parent IDs with IN clause, sort client-side WHERE [System.Parent] IN (1234, 1235, 1236) ORDER BY [System.Id] ``` ## Basic Query Syntax ```bash az boards query --wiql "SELECT [fields] FROM workitems WHERE [conditions]" -o table ``` ## Verified Working Examples ### Query all work items in project ```bash az boards query --wiql "SELECT [System.Id], [System.Title], [System.State] FROM workitems WHERE [System.TeamProject] = 'ProjectName'" -o table ``` ### Query by state ```bash az boards query --wiql "SELECT [System.Id], [System.Title] FROM workitems WHERE [System.State] = 'In Progress' AND [System.TeamProject] = 'ProjectName'" -o table ``` ### Query by work item type ```bash az boards query --wiql "SELECT [System.Id], [System.Title], [System.State] FROM workitems WHERE [System.WorkItemType] = 'Bug' AND [System.TeamProject] = 'ProjectName'" -o table ``` ### Query by assignee ```bash az boards query --wiql "SELECT [System.Id], [System.Title] FROM workitems WHERE [System.AssignedTo] = '[email protected]' AND [System.TeamProject] = 'ProjectName'" -o table ``` ### Query with ORDER BY (most recent first) ```bash az boards query --wiql "SELECT [System.Id], [System.Title], [System.ChangedDate] FROM workitems WHERE [System.TeamProject] = 'ProjectName' ORDER BY [System.ChangedDate] DESC" -o table ``` ### Query by iteration (sprint) ```bash az boards query --wiql "SELECT [System.Id], [System.Title] FROM workitems WHERE [System.IterationPath] = 'ProjectName\\Sprint 1' AND [System.TeamProject] = 'ProjectName'" -o table ``` ### Query by area path ```bash az boards query --wiql "SELECT [System.Id], [System.Title] FROM workitems WHERE [System.AreaPath] UNDER 'ProjectName\\TeamArea'" -o table ``` ### Query with multiple conditions ```bash az boards query --wiql "SELECT [System.Id], [System.Title], [System.State] FROM workitems WHERE [System.WorkItemType] = 'Task' AND [System.State] <> 'Done' AND [System.TeamProject] = 'ProjectName' ORDER BY [Microsoft.VSTS.Common.Priority]" -o table ``` ### Query with tags ```bash az boards query --wiql "SELECT [System.Id], [System.Title] FROM workitems WHERE [System.Tags] CONTAINS 'urgent' AND [System.TeamProject] = 'ProjectName'" -o table ``` ### Unassigned items ```bash az boards query --wiql "SELECT [System.Id], [System.Title] FROM workitems WHERE [System.AssignedTo] = '' AND [System.State] = 'New' AND [System.TeamProject] = 'ProjectName'" -o table ``` ## Common Field Names for SELECT/WHERE | Field | Reference Name | |-------|----------------| | ID | System.Id | | Title | System.Title | | State | System.State | | Type | System.WorkItemType | | Assigned To | System.AssignedTo | | Created By | System.CreatedBy | | Area | System.AreaPath | | Iteration | System.IterationPath | | Created | System.CreatedDate | | Changed | System.ChangedDate | | Priority | Microsoft.VSTS.Common.Priority | | Severity | Microsoft.VSTS.Common.Severity | | Tags | System.Tags | | Story Points | Microsoft.VSTS.Scheduling.StoryPoints | ## WIQL Operators | Operator | Description | Example | |----------|-------------|---------| | `=` | Equals | `[System.State] = 'Active'` | | `<>` | Not equals | `[System.State] <> 'Closed'` | | `>`, `<`, `>=`, `<=` | Comparison | `[Microsoft.VSTS.Common.Priority] <= 2` | | `CONTAINS` | Contains text | `[System.Tags] CONTAINS 'urgent'` | | `NOT CONTAINS` | Does not contain | `[System.Title] NOT CONTAINS 'test'` | | `IN` | In list | `[System.State] IN ('Active', 'New')` | | `NOT IN` | Not in list | `[System.State] NOT IN ('Closed', 'Removed')` | | `UNDER` | Under path | `[System.AreaPath] UNDER 'Project\Team'` | | `AND`, `OR` | Logical operators | `[A] = 'x' AND [B] = 'y'` | ## Macros (Use With Caution) | Macro | Description | Reliability | |-------|-------------|-------------| | `@Me` | Current user | Usually works | | `@Today` | Today's date | Works | | `@Today - N` | N days ago | Works | | `@project` | Current project | UNRELIABLE - use explicit name | | `@CurrentIteration` | Current sprint | May not work in CLI | ## Output Formats - `-o table` - Human readable table - `-o json` - Full JSON output - `-o tsv` - Tab-separated values ## Tips 1. **Always quote string values**: `'Active'` not `Active` 2. **Use brackets around field names**: `[System.State]` not `System.State` 3. **Escape single quotes by doubling**: `'It''s working'` 4. **Path separators use backslash**: `'Project\Team\SubArea'` (double in bash: `'Project\\Team'`) 5. **Always include project filter**: Add `[System.TeamProject] = 'Name'` for reliable results ## Parent Filtering Pattern Since ORDER BY [System.Parent] is not supported, use the IN clause to filter by parent: ```bash # Find all children of specific parents az boards query --wiql "SELECT [System.Id], [System.Title], [System.Parent] FROM WorkItems WHERE [System.Parent] IN (1234, 1235, 1236) AND [System.TeamProject] = 'ProjectName'" -o table ``` This works well for: - Finding all tasks under specific features - Listing child items for a set of parent work items - Building hierarchies by querying children of known parents
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.