Skip to content

Bcup export->import should remain the same #60

Description

@ldexterldesign

Hi!

Thanks, as always, for software

I have a use case for you...

Tonight I wanted to update my vault password

It seems this is non-trivial

I presume I have to:

  1. export my old vault data
  2. create a new vault
  3. import my old vault data to new vault

... if correct then the most useful export/import method (i.e. Buttercup CSV) seems to export all old vault custom fields (i.e. from every entry) to each new entry in the new vault

For example:

Vault

Entry 1

entry1field1: entry1field1value1
entry1field2: entry1field2value2
entry1field3: entry1field3value3

Entry 2

entry2field1: entry2field1value1
entry2field2: entry2field2value2
entry2field3: entry2field3value3

CSV (export)

entry1field1, entry1field2, entry1field3, entry2field1, entry2field2, entry2field3
entry1field1value1, entry1field2value2, entry1field3value3,,,
,,,entry2field1value1, entry2field2value2, entry2field3value3

Is this expected behaviour?

I would expect, by default, if the entry has no field value then don't show the field..?

IMO the export/import feature is currently redundant/unusable as I wouldn't want tons of superfluous/empty fields in all my entries 😕

Hope this is useful and to hear back

Sincerely

PS if this is, indeed, a problem then I suppose it's higher priority than solving my original use case 🤪

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions