Currently, search terms in the searchbar or in table quickfilters are regular expressions. This is a nice feature, but most of our users don't realize it and have trouble when searching for special characters (example string: "15.1(3)M1"). We should change this behavior in the following way:
text search terms should be handled as usual strings
add additional search type “regex“ which can handle regular expressions
interpret all input as usual strings
Did some first testing in the search bar. Could that be, that you inverted the “Text“ and “Regex“ search types?
Search for “15.1(3)“:
matches customer number “15213“ in my example database but not “15.1(3)S1”
matches “15.1(3)S1“ but not customer number “15213“ in my example databsse
Also, the quick filter above the object tables still interpret the search string as regex instead of text
Did some testing and found the following issues:
Search for “15.*“ does not produce search results
quick search in tables has not changed.
Thanks, perfect. The quick search part should be implemented within NET-648
Changed the Jira Workflow from DATAGERRY -> DATAGERRY 2.0