You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a feature request for one feature, not a question, discussion or multiple features.
This is not a feature request for the browser extension or another client.
This feature is not already requested on Github (I've searched it).
This feature does not already exist (I checked the wiki).
Current Status
Currently, there is no way to manage duplicate password entries. If you have moved browsers or managers over the years (or you are old enough that your passwords list predates synced password tools), you will have duplicates.
It seems like the Bulk actions work might need to be merged first, in order to provide some of the needed features and UX.
Feature Description
Duplicates are shown in a special folder, stacked or grouped together in the list
User can choose which duplicates for a given group to merge together, and which is the primary (its existing fields don't get updated)
Once flattened, passwords are no longer shown in the Duplicates folder
Additional Context
Similar to how BitWarden handles it.
The text was updated successfully, but these errors were encountered:
This list is not just a list of duplicate password entries as many might think, such as multiple imports, which would then share the same username/URI/password, which is what I would like to work on clearing, instead of picking through other items that might just have a shared password but aren't actually duplicates from importing.
Current Status
Currently, there is no way to manage duplicate password entries. If you have moved browsers or managers over the years (or you are old enough that your passwords list predates synced password tools), you will have duplicates.
It seems like the Bulk actions work might need to be merged first, in order to provide some of the needed features and UX.
Feature Description
Additional Context
Similar to how BitWarden handles it.
The text was updated successfully, but these errors were encountered: