Details
-
Bug
-
Resolution: Duplicate
-
Highest
-
None
-
10.71
-
None
-
3
-
Severity 1 - Critical
-
Batman! - SCORP5
Description
Issue Summary
Users export features from the feature grid, then import the file (without making any changes) and receive an error stating that the file can't be imported due to the file type being xml. The odd part here is the user never modifies or changes the file type and the file type extension is still xls.
Steps to Reproduce
- Step 1 - Navigate to feature grid
- Step 2 - Export features
- Step 3 - Make a small change to the file by renaming, but don't modify the workitems (Make sure you keep the file type xls)
- Step 4 - Import the renamed file
- Step 4 - Notice Error (System thinks the xls file is xml)
Expected Results
The export template should be xls, and import successfully.
Actual Results
Export file is xls, but the system is recognizing the file as xml.
Workaround
Support had to send customers an export template from our internal instance, modify it to ensure no data was there. Then the customers cut and paste the details from their file to ours, and then import their records.
Attachments
Issue Links
- duplicates
-
JIRAALIGN-1352 [JIRAALIGN-1352] Custom Fields: User is allowed to create Custom fields with same titles
- Closed
- resolves
-
ALIGNSP-3542 Loading...