We're updating the issue view to help you get more done. 

Make regex in search optional

Description

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:

  • search bar

    • text search terms should be handled as usual strings

    • add additional search type “regex“ which can handle regular expressions

  • quick filter

    • interpret all input as usual strings

Activity

Show:
Michael Batz
November 4, 2020, 8:19 AM
Edited

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)“:

  • type “Text”

    • matches customer number “15213“ in my example database but not “15.1(3)S1”

  • type “Regex“

    • 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

Michael Batz
November 5, 2020, 2:10 PM

Did some testing and found the following issues:

  • Search for “15.*“ does not produce search results

  • quick search in tables has not changed.

Michael Batz
November 6, 2020, 10:35 AM

Thanks, perfect. The quick search part should be implemented within NET-648

Michael Batz
November 18, 2020, 10:35 AM

Changed the Jira Workflow from DATAGERRY -> DATAGERRY 2.0

Done

Assignee

Michael Batz

Reporter

Michael Batz

Labels

Story Points

3

Tester

None

Sprint

None

Fix versions

Priority

Medium
Configure