Thank you for the suggestions; if I understand correctly this would require me to do a search for each organization in my vault ā thatās 500-ish searches. Which, yeah, I could do that, but itās a lot to ask of new users. As opposed to a quick scan down the list, which is what Iād be doing if I could sort the vault by domain.
Searching for re-used passwords will not flag identical domains with different passwords ā such as when one entry has the current password and one entry has the old, outdated password that I would like to delete. And it still doesnāt put the flagged entries side-by-side, so if foo.com has a re-used password, I have to scan the entire list (or do a search) to find the other entry, which might be at a.foo.com or z.foo.com or anywhere in between.
Iāve since noticed that itās not just legacy entries; new vault entries are also created with the full hostname in the name field. So this is an ongoing vault maintenance issue, not just a problem for new users.
The root of the problem here isnāt that I have duplicate entries; the root of the problem is that the Vault is sorted by hostname, which isnāt useful at all; rather than by the domain, which is actually quite useful.
This is just the default name. Good practice is to specify a more useful item name during the login item creation process.
Also, for your reference, Bitwarden originally (until April 2018) did use just the base domain as the default name for new login items, but this behavior was updated to the current default naming system (using the FQDN) in response to a feature request.
It is sorted by the value of the Item Name field, which does not have to be the same as the website hostname (FQDN).
If you have 500-some imported vault items, and each domain has an average of 2ā3 subdomain variations, then it would be closer to 200-ish searches. And for your purposes, the best search expression would be the following:
>+name:*foo.com* +login.uris:*foo.com*
I understand that this would still be a lot of manual work.
Your best approach may be to re-do the import after conditioning the data. For example, if you already have a CSV export (or if you create a CSV export from Bitwarden), then you can use a spreadsheet app formula to strip the the subdomain string from each login item name, or even to transform support.foo.com into something like foo.com (support). When the item names have been suitable modified, purge all login items from your vault, and import the modified CSV.
If you need help with the above procedure, please disclose which spreadsheet apps (e.g., Excel) you have available.
Hi everyone, based on feedback, we split the sorting options and expiration reminders back out into their own threads, so feel free to drop a vote here again: Expiration Reminders (rest assured the Bitwarden team retains the same rank/ordering of the previous votes internally)
+1, Sorting options are one of the most used feature of a password manager. Still canāt believe after all these years it still hasnāt been implemented, they would get lots more users if it was. Itās the main reason I donāt use it, sad to say.
ā+1ā does not count as a vote. To vote, spend a half-hour or so browsing various topics in the community. After a while, you will receive a notification that you are elevated to ābasic userā, which gives you 20 votes. At that time, you can come back to this FR and click the blue āvoteā button up at the very top of the topic.
I will add myself to this list. Iāve been using bitwarden for 6 years with subscription for all that time. And lately I also miss this feature more and more. I have over 400 entries and I would really like to sort by last edit date at least. Thank you.
Coming to Bitwarden from NordPass, and I greatly value the ability to sort by last-accessed and last-edited. I only made this account so that I may add my vote in support of this feature.
