User-unfriendly and fragile workflow for updating passwords?
I'm using the 1password app on MacOS. I have a password stored there that I need to change. This password is associated to the site I'm using it on. I would like to keep the old password just in case, for example if I need it to update the client on another device, if the update fails because the password is too complex and I have to enter the old password again, whatever, I just don't want it to be instantly forgotten because I'm not yet totally sure I won't need it again. I thought that was handled by the archive, but that does not seem to be an option.
At first I created a new password with the same website indicator, now I duplicate it and edit the "original", then after some time I get rid of the copy.
Is there a better way?
My ideal workflow would be that if I edit (or call it "update" maybe) a password, the old version is archived and I can access it if needed. The archive would have some indication that "this version was active from xxxx-xx-xx to xxxx-xx-xx". I want some reassurance that things will not just disappear even if I replace them with a new version.
1Password Version: 7.9.10
Extension Version: Not Provided
OS Version: 13.3.1
Browser:_ Chrome
Referrer: forum-search:https://1password.community/search?Search=renew%20password