1

Current behavior:

When users try to find a resource for a specific Task in the "Task" tab of a Project record, it doesn't show any result (No results found) if they put only 2 characters.

To show the result correctly, they need at least 3 characters at the first time. (Once the result is cached, next time it shows the result even with 1 character.)

Also, it doesn't allow any kind of ambiguous search or wildcard search. 

 

Issue:

  • "No results found" message with 2 characters may give a wrong impression that the resource that they are trying to find actually doesn't exist.
  • Once the result is cached, next time it shows results even with 1 character. This can be confusing as well.
  • This can be inconvenient especially in the countries that uses multi-bytes characters.
  • People in those countries tend to have a first and last name with a single character. So the name of the resource can be like "森 実" (MORI, Minoru) or "王 睿" (WANG, Zhiui). In this case even with a space between first and last name, they should put a full name. 
  • How the keyboard input works for those language is 1) enter alphabetical characters 2) hit "transform" key or space bar in the keyboard, then candidates are shown under the character 3) choose the correct character and hit enter
  •  For "森 実" (MORI, Minoru)'s case, users need to 1) enter "mori" first 2) hit a space key to show candidates, choose "森" with up/down keys and hit enter to fix the character 3) hit a space key 4) enter "minoru" 5) same as 2 but for "実". 
  • This is a lot of effort. It would be great if users can find a resource with a single character.

Ask:

1. Please allow to search with 1 character.

2. Please allow wildcard search

3. If not possible, at least change the message like "you need at least 3 characters to perform a search" so users don't misunderstand that resource actually doesn't exist.


STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for your feedback. Currently this is not in our roadmap, however, we are tracking it and if we get more feedbacks and votes, we may consider it in the future.

Sincerely,

Gilberto Onodera
PM, Microsoft