Username data field is skipped when importing data from Proton Pass

Ask the Community Password Manager
,
4

And it’s ignoring Proton’s alias type. Here’s what the alias type looks like when exported in JSON format:

{
  "itemId": "<ITEM_ID>",
  "shareId": "<SHARE_ID>",
  "data": {
	"metadata": {
	  "name": "<ALIAS_NAME>",
	  "note": "<ALIAS_NOTE>",
	  "itemUuid": "<ITEM_ID>"
	},
	"extraFields": [],
	"type": "alias",
	"content": {}
  },
  "state": 1,
  "aliasEmail": "<ALIAS_EMAIL>",
  "contentFormatVersion": 5,
  "createTime": XXXXXXXXXX,
  "modifyTime": XXXXXXXXXX,
  "pinned": false
}

I know Bitwarden doesn’t officially provide an alias email service yet, but instead of ignoring it, Bitwarden could definitely handle this type of data as a Note:

  • Name is the value of <ALIAS_NAME>.
  • Note is the value of <ALIAS_NOTE>.
  • Then create a custom field Alias ​​email (or Email depending on your preference), the value of <ALIAS_EMAIL>.

This would be very useful.