Self troubleshooting

• I've read the documentation and made sure to follow it.
• I've read the troubleshooting first steps and frequent issues guides.

Version

1.10.2

Description

In the Admin interface, when using the Search tool to look for a specific string in All Fields, the string to be searched for is not found found due to case sensitivity. When searching just the Title field, the same search returns the expected results.

In other words, searching the Title field only is case insensitive, but searching the Title field along with other fields becomes case sensitive. This is counterintuitive and confuses users.

I can understand why a search of the urls themselves would be case sensitive, URLs may be case sensitive, so it would be useful to make that distinction. But in the case of text titles and descriptions, this is a lot harder for users to understand.

This creates a situation where a user can search for a keyword they just added and not find it because they forgot what case was used.

Expected Behavior

When searching for a keyword or phrase in all fields, if that keyword is found in the title, I expect the search to find that keyword in the title, just as it does if I search just the title field.

The inconsistency between how the same search term is treated for the same data field is confusing.

Steps to Reproduce

1. Identify a mixed-case keyword in the title of a URL entry
2. Enter the lowercase form of this keyword as a search term in the search UI with All Fields selected, and no records are returned.
3. Search for the same string in the same UI with only the Title field selected, and matching records are returned as expected.
4. Other variants of this behavior also occur (uppercase, mixed case, lowercase)

Context

This is in the Admin interface when searching for URL records. This issue causes end users to think there is no matching entry already in the system, so they end up creating new copies of the same URL, or find incorrect ones.

Ideally searching the title should always be insensitive (because users are likely to be inconsistent when typing in descriptive text) regardless of whether searching title alone or all fields.

Alternatively, an option to enable/disable case sensitivity would offset this issue.