microsoft / microsoft/wiql-editor

Tags: wildcard query not supported? 🤷

Open
#41 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
8
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
The wiql-editor supports Tag queries of the query form ✅
But it doesn't offer any additional capability, on the querying of Tags 😭

Environment:

  • all

Screenshots

  • not applicable

To Reproduce

  1. In your Azure Boards project, select the Wiql editor menu nav option
  2. Create a query with the existing capability: AND [System.Tags] CONTAINS 'Release'
  3. But try wildcard and doesn't work: AND [System.Tags] CONTAINS 'Release%'

Expected behavior
Support wildcard for Tag 'contains' queries.
E.g. "Release%" would allow return of all items with Tag starting with 'Release'.
Without this we have to specify each and every Tag instance, which can be excruciating when there are many (dozens or more). I.e. we have Release 1, Release 2, Release 3 on so on ... releasing weekly.

Additional context
The Jira equivalent extension "JQL tricks" supports this, so kinda sets a bar/expectation (justSayin').

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start from the Wiql editor menu entry point and trace how [System.Tags] CONTAINS queries are parsed or generated. Verify the Azure Boards behavior for a prefix wildcard such as 'Release%' and add coverage if the project has tests; done means matching tags are returned without listing each tag explicitly.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.