On 29/05/13 14:28, Anze Staric wrote:
Joachim Dreimann <[email protected]> wrote:
The other option (#123) should take the user to a disambiguation page /
process.
I do not understand, how a disambiguation page could be used as a part
of writing a search query. I will however add #proda-123 to the list
of supported patterns.
On Wed, May 29, 2013 at 1:40 PM, Gary Martin <[email protected]> wrote:
There are a few more long hand versions that it may be worth supporting like
product:proda:ticket:123
I can add product:proda:ticket:123 and ticket:123 as well. Although
queries like blockedby:product:proda:ticket:123 seem unlikely.
I'll attempt to avoid the temptation to say anything more on the first
part with the hope that Joe will clarify what he means.
I agree that the query you specified might be rare - in fact I wonder if
a query of this type would be very rare anyway given that it doesn't
take too long to get to a ticket and look at the relations that are
specified there.
I'm actually hoping that there is a quick way to collect all the
existing patterns of relevance rather than worrying about justifying
whether to include them. This should also help if there are any future
additions to syntax for any reason.
It may be that this kind of query becomes more useful as the number of
tickets involved grows. Something useful to know might be all the
tickets that block another ticket but are not blocked. Perhaps I should
check if this kind of thing has already been implemented!
Cheers,
Gary
