Hello,

Is there a way to add a custom parameter to a query so it will be prompted to the user when he/she double-click the query to open it.

To give you more details, we are looking for creating a query that will accept a list of work item IDs and return all the issues that matches these IDs.

A convenient way will be for us to specify this kind of condition when building the query:

...

And ID In @myIDList

...

We tried that, but it seems to be not supported.

Thanks for your help,

Gaetano.

Unfortunately this is not supported.

Thanks,

Alex

OK.

Any chance you will add this feature in a future release? I will vote for it if this is the case.

Thanks,

Gaetano.

The ability to specifiy query parameters that would prompt for user input on query execution is already being considered for a future release.

Just so I understand more fully why you want this feature, can you provide examples of how you would use this feature?

NOTE: Any future readers of this forum posting are welcome to provide their examples as well.

Thanks!

Great.

My first example will be to be able to create a query that will prompt for a list of IDs (comma separated for instance) and that will return the corresponding work items as the result.

I'd like to vote for this feature too. The first and foremost use of this for me would also to be to type in a work item ID (although, I'd be happy with entering just one ID - but a comma separated list would be fine too). There may be other things that would be nice to be able to prompt for as well (like the username for the assigned to, etc.), without needing a separate query.

-Daniel

Daniel,

A colleague just discovered that the "ctrl + g" keyboard shortcut allows you to jump to a work item by prompting for the item ID. Hope this help

I would like also to add another example of a query with custom parameters: specifying a query that will prompt for some text to find in work items description field.

Gaetano.

Responding to the last few posts...

The input you've provide is great. Its helpful to know *why* you would use a feature, so we can implement it correctly.

I'll make sure that this information is logged, so when we implement this feature we have this supporting customer evidence.

Thanks again,

Our current environment provides an almost query by example filtering to allow searching work items. They could filter by root cause, area, environment, practically anything and I believe this is useful because different users will have different filtering requirements. For example, someone might decide that they want to knock over a heap of small issues and filter by the estimated time.

Similar functionality to what is available in Reporting Services for providing parameters would be ideal.