History for all fields like Password History

Make change history a universal feature for every field. I’m not sure how history shares currently but that would be nice to have a toggle control over if I want to allow the other person to see the change histories.

There have been a few requests asking for specific fields to gain this feature two I could find on a quick search:

Agree, especially the TOTP code is missing in the history. Imagine the disaster if you accidentally delete the TOTP and don’t have a backup of it. (Of course you should have one, but shjt happens.)

To avoid this scenario, I always manually create a custom field “TOTP backup”.

Would be great if I could spare this step going forward.

1 Like

Completely agree; any secret field should have an automatic history. All fields would be good too.

2 Likes

I think Bitwarden could make an account based storage limit and make the user responsible for clearing old history, since you might want to have history for certain fields.

So, for example, the free account could have a 100 MB limit to store all fields with their history (with a button for the user to see and delete history in case of needing more space).

Feature name

  • History for Item notes

Feature function

I save PIN or additional information in notes and I need to change it. But I don’t see an option to see notes update history. This will be very helpful to see past notes data.

Related topics + references

  • Also need to password-protect some items (very secure) like in Lastpass?

Feature name

Enable Username history (similar to the password history feature)

Feature function

A history of all the usernames once used for a Login entry would be incredibly useful.
This would be identical to the password history feature that’s already implemented by Bitwarden.

This is useful in a number of cases:
Some sites like router logins or banking sites do not allow for long passwords, or do not allow special characters in passwords. Having a long and random username becomes an effective method to mitigate brute force or guessing attacks.

Currently using randomized usernames can be potentially dangerous - i.e. usernames can be changed without any history being left behind.
How I mitigate this is to copy the username to a custom field or a note field.

Thanks

1 Like