Favorites are tracked at cipher level rather than on a per-user basis #629

Closed
opened 2025-11-07 06:43:27 -06:00 by GiteaMirror · 0 comments
Owner

Originally created by @jjlin on GitHub (Mar 1, 2020).

Currently, whether a cipher is a "favorite" is a property of the cipher itself, but it should probably be tracked similarly to folders, with a separate "favorites" table that maps users to ciphers. Otherwise, for a shared cipher, when one user sets a cipher as a "favorite", it automatically becomes every other user's favorite too, which probably isn't the intended behavior.

Also, when changing the "favorite" property, the cipher update time probably shouldn't be updated (similar to #884).

Originally created by @jjlin on GitHub (Mar 1, 2020). Currently, whether a cipher is a "favorite" is a property of the cipher itself, but it should probably be tracked similarly to folders, with a separate "favorites" table that maps users to ciphers. Otherwise, for a shared cipher, when one user sets a cipher as a "favorite", it automatically becomes every other user's favorite too, which probably isn't the intended behavior. Also, when changing the "favorite" property, the cipher update time probably shouldn't be updated (similar to #884).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#629