JIRA Import and Export Troubleshooting
- "A comment must have an issue id specified" error during project import
- Assignee field of imported issues are set to unassigned after running project import
- Bugzilla import fails with "Could not create connection to database server. Attempted reconnect 3 times. Giving up"
- Considerations for CSV and JSON comment imports on top of existing issues in Jira
- CSV Import Fails due to Illegal Group Reference Error
- Custom Field <name> has multiple configuration schemes. Importer is unable to extend custom field context automatically.
- Error Importing CSV File - issueId should not be null
- Exporting long URL's to Excel on IE cause "Page not found" error
- Incompatible Greenhopper version during project import in JIRA
- Irrecoverable error while importing data from redmine
- More than one value stored for custom field id error during project import to Jira server
- Numbers automatically change to Date in Microsoft Excel
- Pivotal Tracker Import Results in NoClassDefFoundError
- Project Import fails due to missing projectroleid
- Project import fails with field does not exist error in Jira server
- Project Import Fails With Has No User Associated With The Watch Error
- Project import fails with Missing userKey from ApplicationUser id
- Project import fails with too many errors in Jira server
- Project or XML backup import will lead to NPE
- Resolution date set on unresolved issues after a CSV import
- Sort comments added to JIRA issue Via CSV Import
- Unable to import file attachment from CSV
- Unable to import file attachment from CSV due to NullPointerException
- When exporting issues to an Excel file, The Excel file contains two rows for each issue.
- You must specify a unique project key when importing from pivotal tracker
最終更新日 2021 年 8 月 5 日
Powered by Confluence and Scroll Viewport.