Reordering fields up/down in the list replaces content of the field

Editing a login item in vault, specifically reordering individual fields, causes the content of the field to be overwritten. This happens whether moving item by mouse or by keyboard.

For example, I have additional fields in this order.

RDP username, RDP IP address, RDP password.

Goal: I want to reorder them to RDP IP address, RDP username, RDP password

  1. I grab the field RDP username field by mouse and move it over RDP IP address
  2. The field RDP username is reordered
  3. The content of RDP username is replaced by whatever was in RDP IP address.

The same happens when I press up/down keys to move items. I can confirmed this happens in web app, Firefox add-on, and Windows app.

On Windows, I have this version:

Verzia 2026.5.0
SDK ‘main (e13c4fc)’
Shell 39.8.5
Renderer 142.0.7444.265
Node 22.22.1
Architecture x64

Hello and welcome to the community :waving_hand:

This is most likely the following bug, which may have been fixed, and should be available in the next versions.

Until the fixed build lands, I would treat the custom fields as read-only while testing this. If you need to reorder them now, copy the field values somewhere local first and re-open the item after saving to verify that the actual stored values did not change. For RDP credentials especially, it is too easy to miss a swapped hidden/custom value in the editor preview.

This seems to be a visual bug in “Edit” mode only, so especially as long as only fields are getting reordered this should not lead to any data loss/“corruption”. – On the other hand, of course, taking some precautions is never a bad idea.

I submitted a fix. This needs to be merged.

For anyone still hitting this: the tracked fix is on GitHub as PR #22642 (issue #21250 / PM-39024).

The branch was rebased onto current main today (7377634470 on AMDphreak:fix/custom-field-reorder-values). Reorder uses FormArray removeAt / insert so custom field values stay with their labels, instead of moveItemInArray on the controls only (which is still what main does). The custom-fields spec suite passes locally after the rebase.

The PR is still open (not merged), labeled needs-qa, with no engineer review on the public thread yet. I left a note on the PR and issue asking for QA/maintainer review.

On the “edit mode only / visual” point: if you reorder and then Save, the swapped values in the form can be written to the vault—so copying values out first (as suggested above) is still wise until a fix ships.

To my knowledge, this was fixed in July:

 

I can no longer reproduce the issue (at least not in the browser extension). If you are still experiencing this bug, could you share what client app or extension you are using (including the version number)?