While this topic is being discussed, I'd actually like to call attention to a closely-related but different shortcoming that's bitten me twice in as many weeks. Namely, it'd be a really massive intermediate step if you were to enable entry history on all password fields in items, and not just the primary field that's present when creating a new item. I'd actually take it one step further and practically implore you to activate entry history for all password and TOTP fields regardless of whether they're system or user created, be there two such fields or twenty. Those are by definition the datums that, if we're doing our personal infosec right, we'll have vanishingly miniscule hope of having any memory of or ability to infer.
I often find myself creating second and third password fields to manage things like credentials with elevated permissions or "In Case of Emergency, Break Glass" API keys/secrets that I want to maintain some kind of record of, but that aren't significant enough to warrant a separate API Credential item for in the Vault. I've had the misfortune of changing a couple of those auxiliary passwords lately that appeared successful but later proved not to be, and I think it just makes sense, not just from a functionality angle but also as regards the UI; the first time it happened I looked every bit the part of the simian trying to fornicate with the football as I hadn't ever considered that the automatic password field in items would be any different from those I added later myself.
That said, please record my concurrence with the OP that the apps should provide access to full histories for all fields, as well as the ability to erase those entries individually or en masse per field.
