Search for "teams" is not working properly.

[lovettchris]

Describe the bug
I'm trying to create a new repo using https://repos.opensource.microsoft.com/orgs/microsoft/new and it requires a "admin team", so i created a new team here: https://github.com/orgs/microsoft/teams/ada-team but the find team dialog is not finding it:

When I search for "ada" it finds a million substring matches which also makes it impossible to find. Can you fix the search box so it works on "whole word" or support double quotes searches like "ada team" that finds exact literal case insensitive match?

Deployment environment
This bug report is intended for issues relating to the project, and not a particular instance of the
management portal. If you are looking to file a bug report about the app itself, please instead
locate the links for support in the footer of every page of the app that you are using.

To Reproduce
See above.

Expected behavior
Search box needs to work better.

Screenshots

Additional context
Add any other context about the problem here.

[jeffwilcox]

Thanks for the feedback, Chris.

Any chance you used the "refresh" button on the right at any time, or just the search experience?

[lovettchris]

Yes I was clicking refresh over and over, but I think I know what happened, the team was showing up here and it seems whatever teams are prepopulated there do not show up in the "Other teams..." list.

But it does show up today, so is there just a very long delay in updating this list?

[jeffwilcox]

Ah, yeah, that must be it. On the GitHub side it can take over 20m to get the list of teams updated in the Microsoft org when someone requests a refresh.

[lovettchris]

would help to perhaps say that somewhere on the site so I can not fret, grab a coffee and come back to it :-)

[github-actions]

This issue has been identified as stale because it has gone 30 days with no activity.
The issue will be closed in 10 days. If this is incorrect, simply comment on the issue, or remove the stale label.

[jeffwilcox]

It's my understanding this issue in the Microsoft-internal instance has been fixed.