Indicate date when vault item last filled into site

[bit]

Currently, Bitwarden shows the date when a password was last changed for a vault item. This is excellent.

I would like to see this extended to show the date when a vault item was last filled into a site.

Here’s a specific use case: I have many email accounts, some of which are rarely used. But my email provider requires a login every 6 months, else they will close the account. Thus I would like to see the date I last used a vault item so I can tell if I’ve logged in during that time period.

[Nail1684]

@bit That may be more difficult than it seems, as Bitwarden also considers – in a more broad sense – using the copy buttons (copy & paste) and using drag & drop as “autofill options”. So, should using those autofill methods count as “last filled” or not?

I think you might profit from this other feature request here as well (i.e. using expiration reminders probably would solve your issue as well – essentially for that feature it wouldn’t matter if the password or the account expires…):

Expiration Reminders for all vault items (including repeating intervals)

Please add a field “Expiry Date” where I can define a date when a password has expired (or will expire). I use this in KeePass to mark passwords that have expired. These password have a red “X” symbol over the Favicon and are not used when I log in via the hotkey. GitHub issue: Add an expiration date to passwords? · Issue #163 · bitwarden/server · GitHub

PS: And I think, without a sorting option for “last filled”, it would become tedious to search hundreds of vault items for “last filled”…:

Sorting Options (by date of modification, addition, last use etc.)

Would be nice to have sort by name / modification date (descending) in folder view and all view. EDIT: sort by date of modification, addition, last use, etc

[grb]

@Nail1684

That may be more difficult than it seems

Or it may not be as difficult as it seems, if one is willing to live with a limited definition of what “date last filled” means.

Consider that Bitwarden’s browser extension already keeps track of when a login was most recently autofilled, because when a website has multiple matching login items, the extension sorts matching logins by order of most recent use:

libs/common/src/vault/services/cipher.service.ts

It seems that this is a locally stored property (different for every client), but it seems that the feature request could be implemented by making a global version of lastUsedDate, which would be synced across clients.