Troubleshooting common issues related to Assets CSV import

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

    

Summary

One of the most frequently used imports in Assets is CSV import. This is particularly useful if this is the most adequate source to import assets from other systems if they cannot be integrated with Assets.

This page summarizes and links knowledge articles that address most frequent issues around CSV import and explain how to resolve them. Some are related to import configuration, but most are related to CSV file formatting.

Most common types of issues related to Assets CSV import and their relevant knowledge base articles and bug tickets



Providing data to Atlassian Support

If none of the KB article listed above helped resolve the issue you have with CSV import, you can also reach out to Atlassian Support via this link. To help the Atlassian support team investigate the issue faster, you can follow the steps below and attach all the collected data to the support ticket raised with Atlassian:


Data to provide to Atlassian Support
  • Collect the following screenshots:
    • Import configuration:
      • On the menu bar, go to Assets > Object Schemas > select the  ⚙ icon in the right corner for the object schema in question >  Configure
      • Go to Imports tab
      • For the import in question, expand the configuration > take a screenshot of it
      • Expand the Object type mapping configuration > take a screenshot of it
    • Object type attributes configuration
      • On the menu bar, go to Assets > Object Schemas > select the schema in question
      • Select the Object Type in question > Attributes > take a screenshot of attributes definition
  • Enable extensive debugging for package, mark the logs and reproduce the import error:
    • Go to Logging and profiling page > Default Loggers section > click "Configure logging level for another package."
    • Add com.riadalabs.jira.plugins.insight.services.imports.schema.log.ImportLogger package with DEBUG level
    • On the same page, mark the logs with IMPORT - START message optional message
    • Manually run the problematic import
    • Mark the logs with IMPORT - END optional message
    • Go back to the Logging and profiling page > find com.riadalabs.jira.plugins.insight.services.imports.schema.log.ImportLogger package on the list and set the debugging level to WARN
    • Generate a support zip on each Jira node
  • Attach to the support ticket:
    1. The screenshots
    2. The support zip(s)





Last modified on Dec 22, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.