On 29 May 2013 14:28, Anze Staric <[email protected]> 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.
Not at the point of writing the query, but after the user has submitted the query. User searches for "#proda-123" -> redirected to ticket. User searches for "#123" -> shown a disambiguation page. That may just list all tickets that end in 123, for example: "#proda-123, #prodb-123, #prodc-123". Style could just be search results. Remember that search is always global (we had many discussions about this in the past). - Joe > 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. > -- Joe Dreimann | *User Experience Designer* | WANdisco<http://www.wandisco.com/> @jdreimann <https://twitter.com/jdreimann>
