-
Suggestion
-
Resolution: Unresolved
-
3
-
31
-
Issue Summary
When trying to import Issues via CSV into Next-gen Projects in Jira, the CSV importer fails to assign the Issues to the defined Issue Types and assigns it to a default Story/Task Issue Type.
Environment
- Team managed Project
- External System Import
Steps to Reproduce
- Prepare a CSV file with the Issue Type header with defined values (Epic, Bug, Custom,...)
- Import the CSV file into a Next-gen Project
- In the field mapping step, map the Issue Type field to their respective Issue Types
Expected Results
- Issues are created as the defined Issue Types from the file (Epic, Bug, Custom,...)
Actual Results
All of the Issues are created as a Story or Task Issue Type (varies per Project).
Workaround
- Import the CSV file into a Company Managed Project instead
- Move the issues from the Company Managed Project to the Team Managed Project
- causes
-
JSWCLOUD-18715 Unable to perform direct migration of the project from cloud to cloud due to CSV import bugs with Next-Gen projects
-
- Closed
-
- is duplicated by
-
MIG-404 Cannot import data into next-gen project custom fields with CSV import
-
- Closed
-
- is related to
-
JSWCLOUD-17829 Team-managed (formerly next-gen) - CSV Import - Failed to assign Epic as IssueType
-
- Closed
-
- is referenced by
-
ENT-1260 Failed to load
Form Name |
---|
[JRACLOUD-82756] CSV imports does not map Issue types for Team managed projects
UIS | Original: 6 | New: 3 |
UIS | Original: 5 | New: 6 |
UIS | Original: 3 | New: 5 |
UIS | Original: 2 | New: 3 |
UIS | Original: 3 | New: 2 |
UIS | Original: 5 | New: 3 |
UIS | Original: 7 | New: 5 |
UIS | Original: 9 | New: 7 |
UIS | Original: 10 | New: 9 |
UIS | Original: 12 | New: 10 |