#450: TracLinks for BloodhoundSeach plugin - after #390
-------------------------+-------------------------------------------------
Reporter: olemis | Owner: nobody
Type: task | Status: new
Priority: major | Milestone:
Component: search | Version:
Resolution: | Keywords: search TracLinks bep-0004
| bep-0004-stable
-------------------------+-------------------------------------------------
Comment (by jdreimann):
I believe this local/global scope change of the search will prove
confusing and annoying to the average user. Search should always remain
global in scope.
Our MultiProduct equivalent to TracLinks should require stating the scope
to be valid and otherwise take users to a disambiguation page.
See the following scenarios:
Input: {{{#1}}}
Output: {{{Did you mean: #PRODA-1, #PRODK-1, #PRODX-1}}}
Input: {{{#PRODA-1}}}
Ouptput: {{{Redirecting to PRODA-1}}}
This should always be the behaviour, also for others objects like Wiki
pages, Milestones, etc. While I am browsing ticket {{{#PRODA-1}}} (so I am
in the {{{PRODA}}} scope) and insert a link to {{{#5}}}, it will lead to a
disambiguation page (though {{{#PRODA-5}}} may be pushed to the top
because it is likely relevant).
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/450#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
