#1776 Importing a 2.X KDBX puts inbound root entries in wrong folder

[caius jard]

A KDBX was created by a third party, with the following structure:

OtherPersonsDBName (2 password entries)
 +- General (0 entries) 
 +- Windows (0 entries)
...
 +- Recycle Bin (2 sample entries)

After importing the other person's DB (using "create new IDs" mode), my database was left with the following structure:

My Password DB Name (2 password entries)
 +- MyGroupName1 (20 entries)
 +- Recycle Bin (my bin)
...
 +- OtherPersonsDBName (0 entries
 +- General (0 entries)
 +- Windows (0 entries)
...
 +- Recycle Bin (other bin, 2 sample entries)

The 2 password entries from the other person's DB (the ones I wanted) were not placed in the folder named with the same name as the imported DB, they were placed in my root folder

No dialog box was shown confirming a successful import

To resolve this bug I suggest either

1) Import the DB and make a new structure inside the imported DB that reflects exactly the structure being imported. The root node in the source database shall become a subnode of the master node in the destination database:

My Database
 +- MyGroup1
 +- MyGroup2
 +- OtherDatabaseName.kdbx
  +- OtherGroup1
  +- OtherGroup2

or
2) Show a dialog after import confirming what nodes in the destination database had new information added and how many imports were made into each node

[caius jard]

Note, when i said "20 entries" I wasnt meaning to imply that the import process had somehow replicated passwords 10 times - they were my existing entries. The complaint is that the 2 passwords out of the source database root folder had been put in my root folder, not the folder created with the source database root name, during import

[Dominik Reichl]

This is the intended behavior. The root group of the imported file always corresponds to the root group of the database. The 'OtherPersonsDBName' group is created during the import only to ensure that no group properties are lost.

Best regards,
Dominik