Filtered search: intelligent filtering
1. Be more flexible with syntax and allow more natural language in the filters.
- If a user types in 12.1 for example, can we assume they mean %12.1 and apply %12.1 (or ~"", @, etc)? This allows users that are not experts in our syntax to easily use the search.
- For example: I propose we allow users to enter either label = ~accent OR label = accent and have it return the same results. This is currently not the case even though it looks like the label has been applied correctly:
2. Suggest/Detect possibly similar Label, Milestone etc.
Taken from comment: !19011 (comment 265010473)
accent should convert to
Accent. Since labels are case sensitive, writing
accent will yield no result but
Accent will. When a user types
accent we know it's non-existent and can be replaced safely with a label which does exist: