CSV Import Export bug?

[webrod]

Hi,

I would like to know whether it is a bug or If I misunderstand something.
THe scenario is very simple:
1- Do a CSV export, with a specification including only Requirements. Include only the GUID and Name attributes. Set the preserve hierarchy to Yes. => a CSV file is created with requirements
2- Now Do a CSV import of the CSV file(do not even update the CSV file)
=> Requirements disappear!! Actually you can find them with a search (CTRL-F), but they are not anymore available in the project browser!

OK I could undesrtand it is because I have to include the "Package" attribute in the "default type" option when I specify the export.
But, as far as I know, I have not included the "Notes" attribute for instance. And the "Notes" of each requirement has been preserved.
It is logical, the process should be "as far as an attribute is not included, it shall be preserved".
Why would it be different for the link to a package? Actually all other links (link with other elements) have been preserved.
At least, all requirements shall appear somewhere, maybe within the same package, like the root, but my god they shall not disappear.

It's the same behavior if you do not check the "preserve hierarchy".
OK, as mentioned above, at least there is a solution if you check the "preserve hierarchy" option AND if you include the "package" element in the specification.
But if you do not check the "preserve hierarchy" option, there is NO way to import exported elements. I even tried to export all attributes and didn't specified any "default types". In other words, everything have been exported.
After the import, EVERYTHING (Requirements, use cases and so on) disappear (except diagrams and packages).

What do you think?
Thanks
Rod
PS: I have the latest version and Build of EA (7.5 844)

[Corey]

11 years later on version 15.0.1513, we're encountering this same bug.

There's no bulk tag editing within EA that we can find, so we've been relying on CSV export and import to apply large numbers of tags. The export/import tool does not seem entirely reliable, sometimes moving everything to the package root when working with a structured package, and at the very worst, this bug where the items simply disappear from the browser but still exist because they're searchable.

I'm using an export/import specification that sometimes works and sometimes causes this bug without a clear pattern. The fact that we can't use these tools without trusting it won't loose data is a major problem.

Specification Settings:
- Delimeter: ,
- Default Types: requirement,package
- Preserve Hierarchy: Yes
- File Specifications: Type, Alias, Name, Notes, <<some various tag values and notes>>, GUID

CSV Import/Export Settings:
- Include Subfolders: Yes
- Export Column Names: Yes

[qwerty]

Why in the world do you use CSV to im-/export? CSV is flat while you model has a tree structure (actually it's even more complex than a tree). Use XMI to ex-/import.

q.