-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Bitwarden desktop client does not update the vault item Name or Username values within the vault item list. #13747
Comments
Thank you for reporting this issue! We've added this to our internal tracking system. |
Similar behavior applies to editing an item's folder. |
I think we need to start using the version numbers where this is a problem and then the version number when/if its fixed. The issues with the screen not updating new field information and ther visual bugs started after It continues to be a problem in every version since up to and including 2025.2.1.exe. I would advise the team/programmers to My workarounds have been.
Direct link to the installer or windows portable versions. That will get you by until the issue is fixed which is not as of version Bitwarden-Installer-2025.2.1.exe |
I got a update notice on windows verion 2025.2.1 today. I like it auto install it and you know what. The non updated item seems to be fixed but there was no version change its staill 2025.2.1 yet its not the same. |
Steps To Reproduce
1
as itsName
value and save it.Name
value and change it to2
and save again.Expected Result
The list of vault items should display the same
Name
value as what's shown in theITEM INFORMATION
pane.Actual Result
The list of vault items displays the prior
Name
value, whilst theITEM INFORMATION
pane is up-to-date.Screenshots or Videos
Additional Context
The same behaviour can be reproduced with respect to the
Username
field.Operating System
Windows
Operating System Version
24H2 26100.3194
Installation method
Direct Download (from bitwarden.com)
Build Version
2025.2.1
Issue Tracking Info
The text was updated successfully, but these errors were encountered: