#10031 closed enhancement (duplicate)
Search doesn't use milestone/component keywords when finding tickets
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | search system | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
For example if I search on http://trac.edgewall.org for:
grouped query report
I will get 8 results but they will not include http://trac.edgewall.org/ticket/3284
To find 3284 I have to search for
grouped query
but that also finds a lot of other irrelevant results and makes it harder to find the ticket I am looking for.
This is quite limiting for us as tickets n our system do not tend to repeat the name of the component because it is redundant information.
Attachments (0)
Change History (2)
comment:1 by , 14 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
comment:2 by , 14 years ago
The problem with that solution is that you don't always know the component.
Yes the search is indeed slow. I think an indexed search engine that can read our trac pages could be the solution instead.
This could be achieved by #1329, where you could first search for "grouped query", then refine the results with a query restricting the component. So I'm closing this as a duplicate.
The search functionality is already quite slow, so I would prefer not to add any more fields to it.