View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0019302 | mantisbt | filters | public | 2015-01-30 01:42 | 2022-12-11 17:59 |
Reporter | vboctor | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Product Version | 1.3.0-beta.1 | ||||
Summary | 0019302: Free text search should match against tags | ||||
Description | I've noticed that if I put in a tag in the free text search field, i get N entries. But if I put the same tag in the tags field, I get > N matches. This means that we are not doing text search against tags. | ||||
Tags | No tags attached. | ||||
has duplicate | 0011976 | closed | cproensa | Search by Tag |
related to | 0007183 | acknowledged | new search function on field and custom field | |
related to | 0024750 | acknowledged | Allow text entry for search with partial match in custom fields filters | |
related to | 0011467 | new | Bug view page search within customized fields |
What's the rationale for searching tags via text search ? IMO, free text search applies to text fields, so it makes sense that tags are not covered. If a user wants to search by tag, they should use the dedicated field. |
|
Typically free text search is a way to look across all aspects of an item. This includes content, meta-data, etc. Searching via tags, will just give tags. Currently it covers the following fields:
The question is whether we should add not just tags, but:
i.e. almost search everything vs. just few pre-canned fields. Think of it as the Bing/Google of the bug tracker. |
|
It seems, it will not be implemented in matisbt directly. |
|
Not sure if this can be done with current approach for searching. |
|
Whenever someone should start working on that, keep in mind what I commenetd in PR https://github.com/mantisbt/mantisbt/pull/1140#issuecomment-320712837 Strange result, as I got what I expected on one of my test systems. Independant from that, there is a serious conceptual issue. E.g. set Read Access of a custom field to access level manager. |
|
Agree, including tags, custom, fields, etc in the filter search needs more logic to account for user permissions on viewing those items, on a project, or issue level. Additionally, i'm not sure the approach of "search everything" is all that good.
Yes, best solution would be to have a dedicated search plugin, with al lthe advanced functionality, and keep native search more or less simple as it is now... |
|
A workaround might be to allow free text entry into the tags and custom field filters rather than just a drop down box option. 0024750 |
|
AGREE that custom fields should be searchable in free-text search. This is a huge problem for my users. They're very confused by inconsistent search results. |
|