Entries mixed and not sorted by date


Hi, seems like password history entries are not sorted by date, is it a bug ? This happens even in mobile app (android in my case)

I could not reproduce this in the browser extension (2025.12.0) for Chrome in Windows 11; I see the password history sorted in reverse chronological order.

Are you able to reproduce this by creating a new login item, then repeatedly changing its password (e.g., pwd1pwd2pwd3 → etc.)? Or does it only happen when you change the password on items that were last updated years ago?

@superdave In addition to @grb’s questions: is this – or are these – vault items that you (re-)imported into your vault at any point in time?

I haven’t imported anything, I’ve always created them from scratch.

This also happens with more recent entries, so I think it’s clearly a system bug or at least a feature not implemented since it looks like unsorted

@grb to reproduce that you need to wait more days/months :sweat_smile:

Not this part:

You mentioned that you’ve observed the behavior in some recent entries, but you have not confirmed that you can reproduce this behavior at will, by creating a brand new entry (resulting in a randomly ordered password history every time that you perform such a test).

I don’t think I understand, but as I told you, if you ask me to reproduce “that” then you have to try with different days and months because if I change it every 2 seconds what’s the point, given that the dates are the same anyway?

The password history does show the time, including the seconds, so that should be enough, I think…

You will still be able to tell whether the passwords are displayed in reverse chronological order or randomly, because the timestamps shown in the password history do include hours, minutes, and seconds (not just the calendar date). Furthermore, if you name each new password using an incrementing index, as previously suggested (literally: pwd1pwd2pwd3 → etc.), then you will be able to see if the display order is out of sequence, even if you had no timestamp data available.