This has been discussed 4 years ago here, yet I don't see any improvement on 1Password side.
There are many things which are not logins but simply passwords: SSH keys, files and directories, safe locks, bike locks and, to a certain degree, computers (because you're only asked for password, not username when e.g. using
These items do sometimes change passwords, especially the computers. However, 1password does not remember the history.
In my opinion, any password field that can be edited should offer version storage. IF the
Password type is only as a failsafe for unregistered passwords, it should not allow editing by hand, nor manual creation of items of this type.
I am just finding myself frustrated in a situation where I have changed a password stored in one of these fields, but somehow the destination didn't catch it correctly and has left the previous password. Being both randomly generated, I am blocked because I no longer know the previous password
1Password Version: 7.6
Extension Version: Not Provided
OS Version: OS X 10.15.4
Sync Type: Not Provided