|
I don't want to have to weed through bad results. I want to search the issues for "xml doctype exception", see that there are no matches, and file my issue. I don't want to have to browse through every single request which contains "xml" or "exception."
It sounds like the problem here is that JIRA 3.0 returned results effectively unordered. In JIRA 3.2, searching for "xml doctype exception" will return issues with those exact words in the summary first, and subsequent results in order of decreasing 'relevance'. See
Yes, I see what you mean.
I would submit that JIRA's existing search behaviour returns the best results for most people. If you search for "Default search operator", you get this issue as the first hit (keeping exact searchers happy) and get other issues listed, which are often also of interest to searchers. For instance, searching for "Default search operator" also returns the analogous Confluence issue This isn't to say that AND is never valid; just that OR returns more useful results for most people. If you want AND, add && between terms, eg. "Default && search && operator". Keith,
I am not an expert on the matter but I am not sure if google returns only AND results. I believe the results are returned in order of relevance, and hence documents with more words in them are returned first. Thanks, From http://www.google.com/help/basics.html#and
 :
"By default, Google only returns pages that include all of your search terms. There is no need to include "and" between terms. Keep in mind that the order in which the terms are typed will affect the search results. To restrict a search further, just include more terms. For example, to plan a vacation to Hawaii, simply type vacation hawaii." Also, a search for 'big AND teeth" on yahoo produces the same results and number of results as "big teeth." Also, on the results page it removes the AND from the search.
If you use the MSN Search Builder, and you type words in the Search Terms box and select "All of these terms," then click "Add to search," it inserts the words verbatim without any + or AND, which shows that MSN search is also AND by default. I stand corrected - thanks.
I think that this issue should be reopened and reconsidered for a number of reasons. The prime reason is that I strongly disagree with the notion that "JIRA's existing search behaviour returns the best results for most people".
Concretely, when I type the following search phrase into our JIRA installation:
I expect issues containing both the phrase "Error Log" and the word "topmenuen" to be listed at the top of the list, but instead the list is swamped with issues containing only one of the search words, and the two issues containing both words aren't listed first. My theory is that the problem stems from the fact that one of the words is located in the Summary, whereas the other word is located in the Description. Trying to boost the weight of one of the search words using, for example, ^4, doesn't help either. (This just shuffles the results, still without putting results with both words in the top). I've previously filed a support case regarding the issue, but I was told to comment on this issue instead. Another reason for reopening and reconsidering this issue is that AND searches are now the default behaviour in Confluence as well (see the linked issue). Hi,
I want to add my 2 cents to this issue. My original issue was https://support.atlassian.com/browse/JSP-17318 *************** Since confluence is using the AND by default, then why not be consistent. I believe that is what Atlasssian is now pushing with your new JIRA studio. The fact that it is a uniform platform. If you want your platform to be uniform then what could be more important than having a uniform way of searching for stuff regardless of which product I am using? If you guys are really worried about affecting existing users that are used to the OR default, then give me a system parameter that I can set based on my preference. Then this would make everyone happy. Maurizio,
I have reopened this issue. I think having the same behaviour between JIRA and Confluence certainly makes sense. We will definitely keep this issue in mind, however, at the moment, I cannot give the exact implementation date for this issue. Cheers, The same argumentation used here led to success for Confluence users in
I also strongly disagree with the notion that Confluence returns the results in a useful order. For one thing, it would be sensible to return more recent results first among those with equal matching weight. But no, you always get the old junk from ten versions ago listed first. And clearly a match in the title should weight much more heavily than one in the description, but a phrase match in the description should weigh more heavily than a single-word match in the title. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Reopened
Major
Default search operator should be AND, not OR
I am not exactly sure what you mean. Are your refering to free tet searching in issues' summary/description/comments?
If so, JIRA sorts the output by "relevance" so the issues that closer match the input will appear first. Is this not what you are seeing? If you absolutely need to limit the search with an AND operator you can separate the string by &&. For example:
search && for && all && these && strings
Please let us know if I misunderstood your query.
Thanks,
Anton