By clicking on "Manage..." you can see the favorites of all users (provided you have permissions to see the menu item).
In case you do not have permissions to view the menu item, right now:
In SAO it triggers a series of infinite requests (model.ir.ui.menu.favorite.read).
In Tryton it crashes the program.
The user also cannot modify the sequence. IMHO I think that the access rule was right so that the user could order them as he/she liked, now you can't because you need a group to be able to edit.
Step to reproduce (demo 7.2):
Login with admin > Set Parties/Configuration as FAV
Login with demo and click in "Manage..." menu favorites
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
I do not think so because the entries are menu path so for example "Administration" will always be first.
Ideally it would be better to have first the menu the most used but counting clicks on menu seem like a waste of resources.
Of course we could also unset/set the favorite each time it is used but again this will increase the IDs for few benefit.
Another option would be to expand the menu tree to the favorite used, so user can unset/set it easily. But again this is complex code for very low benefit as the favorite name is the path in the menu tree.
I would like to concur: Not being able to sort favorites in the desired order (or having to remove them all to put them in the desired order) is really not user friendly (nor intuitive). And to order them by name for me is only a poor last resort.
I agrre that allowing the user to order the favorites using a sequences seems like the best option.
A simple solution could be to add the favourites on user preferences using a xxx2Many widget which just allows to add/remove or set the order? Like we do for actions that the user is allowed to select which actions are openend by default.
I'm not sure if the order is really needed, just said that it is the best option is to let the user define it. TBH: I've never used it and I do not think any of our users is using it.
It seems you also want to maintain it by keeping the order of the favorites by adding and removing them. But this is a workarround which is causing the dilema.
Having said that I see two options here:
Remove the order and keep a stable order and don't let the user modify it by any mean.
Keep the order but find a way to let the user define it.
Any of the options is fine for me. Of course, as tryton is a flexible framework if we keep the first option anyone that really needs the order can implement some custom code to allow the user.
If you want me to vote on any. I vote for 1. Remove the order.
Favorites until now are an important user space where they are able to put and group their important shortcuts independent from the application menu into a list that makes most sense to them, increasing productivity according to their workflows. This proposal is from the user's point of view not a simplification, but a removal resp. overcomplication of a production feature.