Skip to content

New clone items create password history of the existing password being changed in the clone process. #3898

@shell-surfer

Description

@shell-surfer

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Create a login and add a username and password.
  2. Clone the login and edit the password before saving the cloned item.
  3. Check the password history of the cloned item to see a new password history entry of the current password that is being changed in the clone process.

Expected Result

Cloned logins do not create a password history of the current password or any hidden field that is being changed in the clone process. This is the current behaviour as seen in all other clients.

Actual Result

A new password history entry is added for the existing password that is being changed in the clone process. This usually happens only when you edit a password or a hidden field in an existing login and save it.

Screenshots or Videos

bitwarden_beta_android.mp4
bitwarden-desktop.mp4

Additional Context

No response

Build Version

2024.8.1-beta (19099)

Environment Details

Device - Oneplus 9R
OS Version - Android 14

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions