They recommend you to use a custom field with the date for each entry, so that you know when you have edited a password. But at the end of the blog they boast about their password history feature that will provide the passwords history with the dates they were change.
It sounds like the password history shows generated passwords (e.g , for all entries or for no entry), not passwords saved for an entry. I haven’t tested this yet, though.
If so, it wouldn’t help you with any particular entry’s past password, and in fact it would seem like a pretty useless feature.
I’m a bit confused with the first and last tips.
They recommend you to use a custom field with the date for each entry, so that you know when you have edited a password. But at the end of the blog they boast about their password history feature that will provide the passwords history with the dates they were change.
What’s the benefit of the custom field then?
It sounds like the password history shows generated passwords (e.g , for all entries or for no entry), not passwords saved for an entry. I haven’t tested this yet, though.
If so, it wouldn’t help you with any particular entry’s past password, and in fact it would seem like a pretty useless feature.
They have both, one history where you see all created passwords and within each entry you can see the previous passwords for this specific entry
So yeah, I don’t see the reason for a manual tracking of the date…except if you maybe change something else (name, login etc.)