I need help transferring all issues, including their content, comments, and other fields, from one JIRA project to another on a separate server. I attempted to export the issues to a CSV file and then import them, but encountered problems. Specifically, the exported CSV does not include issue comments, and attachment images are not being imported correctly. I would appreciate guidance on how to effectively complete this migration while preserving all critical data.
Based on my previous experience with JIRA migrations between servers, I’ve discovered that relying on CSV exports can be limiting in maintaining all issue details. CSV files tend to miss nested information such as comments and attachments, leading to potential data loss. In my case, switching to using an XML backup option proved more effective and preserved the necessary details. It is important to conduct a trial migration on a test environment first to ensure that all fields are migrating correctly. In some cases, third-party tools may further streamline the process while keeping configurations intact.
hey, try using jira’s xml back up method – it better handles comments & attachemnts than csv. its not perfect but might be a better bet than device by exporting issues manually. good luck, dude!
In my experience, an alternative approach involves leveraging the JIRA REST API to extract detailed issue data including comments, attachments, and custom fields. I developed a custom migration script that reads each issue from the source server and recreates them on the target server. This method, although more technically complex, allows for precise control over all aspects of the data, minimizing loss. It is crucial to test the script extensively to ensure consistency and integrity of the data, especially when handling custom workflows or configurations.
In my experience, one method I found effective was combining partial XML export with the JIRA import wizard. I faced similar issues with incomplete CSV files initially and realized that the XML export maintained more details, though still required some manual intervention to restore comment threads and attachments. After exporting, I ran a preliminary import in a staging environment and corrected any discrepancies before committing to the live server. This approach may be more time-consuming but ultimately provided a means to ensure no critical data was lost during migration.
hey, try a third party plugin like jira sync since it keeps custom fields and attachemnts intact. i had similar issues with csv and using a stagin test env saved me tons of headaches. good luck with your migtation!