Bug 828080
| Summary: | PRD34 - [RFE] Please allow to search in a case-insensitive manner from the search bar | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | lpeer <lpeer> |
| Component: | ovirt-engine-webadmin-portal | Assignee: | Oved Ourfali <oourfali> |
| Status: | CLOSED ERRATA | QA Contact: | Pavel Stehlik <pstehlik> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.1.0 | CC: | acathrow, dswegen, dyasny, ecohen, iheim, jhunsaker, lpeer, oourfali, pstehlik, Rhev-m-bugs, tpoitras, yeylon, ykaul |
| Target Milestone: | --- | Keywords: | FutureFeature, Reopened |
| Target Release: | 3.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | ux | ||
| Fixed In Version: | ovirt-3.4.0-alpha1 | Doc Type: | Enhancement |
| Doc Text: |
In versions previous to Red Hat Enterprise Virtualization 3.4, searches in the Administration Portal were case sensitive. Now, the search bar supports case insensitive searches.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-09 14:58:00 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
lpeer
2012-06-04 08:20:58 UTC
is this a regression from the WPF search in the UI? (iirc, search has a flag if to perform case sensitive or not, and iirc, UI is supposed to be case in-sensitive) I think this functionality changed when moving from ms-sql to postgres. I see we have a way to configure case sensitivity in the code, in the search parameters the user can use SearchParameters.caseSensitive false (the default value is true). I am moving this bug to the UI, for it to use case insensetive search. einav - iirc, we were supposed to have a checkbox if to make search case sensitive or not? (In reply to comment #3) > einav - iirc, we were supposed to have a checkbox if to make search case > sensitive or not? You have suggested it a number of times in the past, however no decision was ever made on the matter AFAIK. Livnat is right - this functionality was changed due to ms-sql-to-postgres migration. However, this is not a bug - the search is case sensitive by design since 3.0 (see Bug 710146). I am turning this bug into an RFE for adding a "match case" check-box in the search. * Note that turning search to case-insensitive is extremely bad when in tree-context, in case you have objects within the system that have the same name with a different case. E.g. if I have DC "aaa" and DC "AAA", for case-insensitive search when standing on the "aaa" DC, results for "AAA" DC will also return, which is wrong - need to think about it. Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug. The posted patches change the search to be case-insensitive, as it makes more sense and it is more user friendly. Adding another configuration for that would have made the UI more cumbersome and confusing. This change brings up tree-related issues, as the tree searches are dependent on the case-sensitive name DCs and Clusters, thus in order to solve it, we now prevens creating two DCs/Clusters with the same name but with different case. As stated in Comment #7, the solution changes the GUI search to simply be case-insensitive (without adding a check-box or anything like that) -> changing subject accordingly. *** Bug 1043022 has been marked as a duplicate of this bug. *** ovirt 3.4.0 alpha has been released Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0506.html |