Inconsitency in UI in /apps/memories/recognize

[mc]

Is your feature request related to a problem? Please describe.
When you go to unassigned Faces, and select an image, the button will be "Move Cluster to different Cluster", and there will ne no action point in the menu for "move to person".

However, when you go to a normal Persons view and select an image , the button will be DELETE and the "move to person" needs to be selected from the menu:

Now, i dont mind if the action is not always at the same spot in different views; BUT if the action is in a shortcut place in one view, and the same place is, in another view, used for a destructive action (delete, even with extra confirmation), i would suggest that this is a very bad idea.

I dont know what the enxtcloud mantra for these kind of ui decisions is, so i would not like to suggest the best way out.

[luxzg]

People -> "Some Person" view -> select one or more photos -> then "..." menu:

People -> "Unassigned faces" view -> select one or more photos -> then "..." menu:

Indeed, it also makes it impossible to assign the unassigned face to correct person, as I don't see the option to move a single or several selected photos to another person.

Oh and I don't think this should be tagged as "feature" as it seems like a bug and inconsistency, not a feature request. But I may be interpreting github tags in a wrong way.

Edit: I was just instructed into another discussion (here: nextcloud/recognize#754 (reply in thread) ) that I was missing the "default icon" which indeed offers "Move to person" in the "Unassigned" page. So I appologize for not noticing. But wouldn't "..." menu need to include that option as well? Mouseover/hover is sort of fine, but some people obviously wouldn't notice it (yeah, sorry, I'm that one out of million). And in this case I could agree about this beaing feature request for 1/1000000 users, not a bug... Different UI expectations I guess, right? 🙈