I don't think that really works as there is nothing to say that a user
would not want to modify the search as this is not the ticket they are
looking for. The extra click to get to the ticket is no big deal.
If the id is specified, the expectation changes and we should go direct
to the ticket.
We shouldn't forget that the search is not just within the ticket space
unless a user restricts it to that.
Cheers,
Gary
On 16/10/12 11:02, Peter Koželj wrote:
Unless I am missing something, jumping to ticket only works if user know
ticket id.
Can we or should we enable this for any search that results in a single
ticket?
On Tue, Oct 16, 2012 at 11:44 AM, Apache Bloodhound <
[email protected]> wrote:
#232: Nudge users towards understanding search syntax
--------------------------+--------------------
Reporter: jdreimann | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords:
--------------------------+--------------------
Description changed by jdreimann:
Old description:
,, ... via ''Bloodhound'' quick create ticket dialog,,
New description:
Users can use TracLinks in the search box to jump directly to tickets,
wiki pages, change sets and more. I believe we should nudge them towards
this by displaying a short one-liner at the bottom of the search results
page:
{{{You can jump directly to tickets, wiki pages, change sets and more by
typing a [TracLink] into the search box.}}}
The wording can doubtlessly be improved :)
--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/232#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
