-
Suggestion
-
Resolution: Unresolved
-
11
-
43
-
Summary
The CSV import will fail if a team-managed (formerly next-gen) project's field is mapped during the import.
The following message is displayed:
You now get the following error message:
Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state: At least one given IssueParentAssociations must not be empty!
Detailed logs:
2018-10-31 13:00:36,645 INFO - Import started by admin using com.atlassian.jira.plugins.importer.imports.csv.CsvDataBean 2018-10-31 13:00:36,824 INFO - ------------------------------ 2018-10-31 13:00:36,824 INFO - Importing: Users 2018-10-31 13:00:36,824 INFO - ------------------------------ 2018-10-31 13:00:36,824 INFO - Only new items will be imported 2018-10-31 13:00:36,827 INFO - 0 users associated with import. All of them imported as inactive, this can be changed after import in User Access step. 2018-10-31 13:00:36,827 INFO - ------------------------------ 2018-10-31 13:00:36,827 INFO - Finished Importing : Users 2018-10-31 13:00:36,827 INFO - ------------------------------ 2018-10-31 13:00:36,827 INFO - 0 users successfully created. 2018-10-31 13:00:36,829 INFO - Retrieving projects... 2018-10-31 13:00:36,839 INFO - Project ExternalProject{id='null', key='NG', externalName='null', name='Next gen', type='null', template='null'} exists and found correctly. 2018-10-31 13:00:36,842 INFO - ------------------------------ 2018-10-31 13:00:36,842 INFO - Importing: Versions 2018-10-31 13:00:36,842 INFO - ------------------------------ 2018-10-31 13:00:36,842 INFO - Only new items will be imported 2018-10-31 13:00:36,842 INFO - ------------------------------ 2018-10-31 13:00:36,842 INFO - Finished Importing : Versions 2018-10-31 13:00:36,842 INFO - ------------------------------ 2018-10-31 13:00:36,842 INFO - ------------------------------ 2018-10-31 13:00:36,842 INFO - Importing: Components 2018-10-31 13:00:36,842 INFO - ------------------------------ 2018-10-31 13:00:36,842 INFO - Only new items will be imported 2018-10-31 13:00:36,842 INFO - ------------------------------ 2018-10-31 13:00:36,842 INFO - Finished Importing : Components 2018-10-31 13:00:36,842 INFO - ------------------------------ 2018-10-31 13:00:36,846 INFO - Retrieving custom fields... 2018-10-31 13:00:36,850 INFO - ------------------------------ 2018-10-31 13:00:36,850 INFO - Importing: Issues 2018-10-31 13:00:36,850 INFO - ------------------------------ 2018-10-31 13:00:36,850 INFO - Only new items will be imported 2018-10-31 13:00:36,898 INFO - Importing issue: [externalId='autoid-8429087420537541515', summary='Summary'] 2018-10-31 13:00:36,908 INFO - ------------------------------ 2018-10-31 13:00:36,908 INFO - Finished Importing : Issues 2018-10-31 13:00:36,908 INFO - ------------------------------ 2018-10-31 13:00:36,908 ERROR - Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state:
Environment
Jira Cloud
Steps to Reproduce
- Create a CSV file (example: test.csv
) - Go to the External system import section -> select CSV;
- Select a team-managed (formerly next-gen) project to import the issue to:
- Map the fields (make sure to map one of the target project's fields):
The import is not successful.
Suggestion
Support CSV imports in team-managed (formerly next-gen) projects.
Workaround
Use the cloud to cloud migration tool instead https://support.atlassian.com/migration/docs/perform-a-cloud-to-cloud-migration-for-jira/
- is related to
-
JRACLOUD-73628 Next-gen CSV Import - cannot import data into "Paragraph" field
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is resolved by
-
- Closed
- relates to
-
JSDCLOUD-8262 Unable to import a JSON/CSV file to Service Desk next-gen projects
- Closed
-
-
- Closed
-
-
-
- Gathering Impact
-
- is addressed by
-
ENT-1260 Loading...
- mentioned in
-
-
-
-
-
-
-
[JRACLOUD-82657] Team-managed projects do not support CSV imports
@katelyn, I did this by:
- Selecting cog in upper-right
- Under "Jira Settings", select "System"
- In left-menu, under "Import and Export" select "External System Import"
- I then used CSV import to import issues from an excel sheet
The import wizard in Jira makes mapping straightforward. As I mentioned above, I am able to successfully map data to custom and default system fields using this process. I was also able to link new task tickets to existing task tickets using the "relates to" link. I did not attempt to link these issues to an epic as part of the import.
No JQL was necessary to complete this.
Yes, the import it's working better on Next Gen but still not working for linking Epics and Tasks.
the only way to do this is to import into a Classic project and then use the Bulk function to move issues to the Next Gen.
Or with the REST API.
@Alexander - Could you share some insight on how you did this in Next Gen? What documentation did you follow to complete the import? Did you need to do something specific with JQL?
Tried again on October 1st 2020, and this feature now seems to be working. I successfully imported from a CSV to a next-gen project, and mapped CSV columns to custom+system Jira fields. All mapped data correctly imported to the newly generated tickets.
Previously, when using the same exact process, the import would "succeed" but no custom fields would fill with the mapped data.
Glad this is now working.
"Next-gen" projects should just be called "Lite" projects. It's become clear that if you want a full-featured tool you should stay away from them.
The real bug is in Atlassian's process in that this same request must be over at least 10 issues as near as I can tell. All of them complaining, asking, begging for the same thing. However each of them only has a small number of "votes". If taken in total across these 10 issues that I have found so far the number would be quite large.
This "bug" / "feature request" has been open since next gen came out. Go and look through this Jira and you will see.
Hi Srihari,
The product allows users to do an import. The import does not work as expected. That is a bug.
If you remove the ability to execute the import and provide a nice error message saying "Next-Gen Projects do not support CSV imports at this time" THEN this becomes a feature request.
Hi Team,
I am from development team. We currently don't support next-gen mappings for CSV imports. This needs to be treated as a feature request, and not a bug. Can you please update the ticket to track this as a feature request.
Thanks and Regards,
Srihari
Strongly disagree with the "Medium" prioritization. From the Atlassian Cloud fix Bug Policy:
Priority 2 - High
A feature is unavailable, application performance is significantly degraded, or users job functions are impaired.
Examples:
- the application performs slowly and fails intermittently
- application is functional, but frequently used gadgets or macros don't work
- specific editing features fail
Importing data to custom fields is a frequently used process in every organization I've worked in. I further note in the documentation:
Medium priority bugs are typically worked on after all High and Highest priority bugs are resolved and there are no other critical priorities.
With a "Medium" Priority designation, this bug will not be addressed in any reasonable timeframe, as "High" and "Highest" priority issues are often found affecting the next-gen platform.
I, and I'm sure many of the other watchers, would appreciate an explanation for why this issue is categorized as "Medium" priority. Perhaps Atlassian considers the existence of Classic projects a suitable "workaround" to broken core functionality in Next Gen.
It is working now..