pipes would be OR, so you'd get all subjects with "john" OR "mark" (john||mark) = lots of results&& is AND so you *should* find subjects with "john" AND "mark" using parentheses (john&&mark) (which should also include "john & mark" as a side effect, but not because the ampersand is included).
The Module/AgentTicketSearch.pm assigns the ExtendedSearchCondition to ConditionInline:
my @ViewableTicketIDs = $Self->{TicketObjectSearch}->TicketSearch(
#stuff snipped
ConditionInline => $Self->{Config}->{ExtendedSearchCondition},
The documentation in System/TicketSearch.pm says:
# content conditions for From,To,Cc,Subject,Body
# Title,CustomerID and CustomerUserLogin (all optional)
ConditionInline => 1,
But ConditionInline only appears once in System/TicketSearch.pm:
if ( $Param{ConditionInline} && $Key eq 'Title' ) {
So, either ConditionInline/ExtendedSearchCondition is irrelevant to the search or not applied per documentation.
This, in turn, is called by the DB QueryCondition (System/DB.pm) method:
documentation:
my $SQL = $DBObject->QueryCondition(
Key => 'some_col',
Value => '(ABC+DEF)',
SearchPrefix => '',
SearchSuffix => '*'
Extended => 1, # use also " " as "&&", e.g. "bob smith" -> "bob&&smith"
);
applied code:
# 1. replace " " by "&&"
if ( $Param{Extended} ) {
$Param{Value} =~ s/\s/&&/g;
}
Which seems to be a bit different concept than as originally explained, as this treats a space as "AND".
Long story short: I'd try (john*mark) or (john * mark)