[MGNLCI-30] Support complex structures with the help of sorting the files Created: 31/Jul/23 Updated: 05/Feb/24 Resolved: 05/Feb/24 |
|
| Status: | Resolved |
| Project: | Content Importer |
| Component/s: | None |
| Affects Version/s: | 1.0.4 |
| Fix Version/s: | 1.1, 1.0.5 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Tobias Kerschbaum | Assignee: | Adam Siska |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Team: | |||||||||
| Work Started: | |||||||||
| Description |
|
Suppose you use the Content importer with complex/deep folder structures and export these into several files. In that case, errors occur during the import because the import order is the wrong way around, and therefore, sometimes the required path still needs to be created. Especially when importing test data for repeatable tests, this is necessary. Steps to reproduce: You can observe the behavior if you export Item, Item2, and the folders individually and put them into the content importer. Actual result: Expected result:
We have this requirement both in our internal demo team and specifically from two customers.
|