It would be useful for search but not for much else. To be useful it would need to have a column to display which menu it is in (think the category column in article manager). Otherwise a site with multiple menu items with the same name across multiple menus will be impossible to differentiate.
If it is really an issue then it can be resolved already by using the frontend menu edit links. That ensures that you select the correct menu.
The more complex the site the harder it gets.
This is really a site design issue especially when people dont give menus meaningful names

I agree it is time consuming to search for menu items, even if a site has e.g. 5 menus

e.g. imagine if there was same limitation in article manager

• meaning if you had to select a category before being able to list articles

i understand that the reason behind this is the tree stucture of menus ?

but being able to search in all menus by alias/name/id would be a welcome improvement
of course a new column to show the menu of the item would be needed, and no tree structure would be displayed if no menu is selected

@pe7er I think that it will be useful for search but in terms of performance it could cause some issues if you have many menus. If this is going to be implemented the results page with all items has to be modified as well, so that results will be dynamically loaded from a cached object.

@pe7er have you thought any more on this or shall we close it.

As I said before I can see the value for the search filter but I dont think we can do that without adding a column in the list view itself as well

I have created a PR for this. I did not remark a big impact on performance (anyway it is back-end)
Please test
#8411

closed as there is a PR