Exporting backlog and releases details to csv
Importing existing issues to the backlog
On this page
Related content
- JIRA Cannot Create Issues when Using MySQL with Binary Logging
- Confluence will not start using MySQL 5.1.5+ with STATEMENT binary logging
- MySQL Binary Logging Problem with InnoDB When Creating a Workflow
- Bitbucket Server 2.7 fails to start with MySQL when binary logging is enabled
- Operations in Jira server fail with communications link failure in logs with MySQL
- Jira throws "Could not determine database type Unknown storage engine InnoDB" when starting
- "Communications link failure" Error with JIRA User Management on MySQL
- Various issues are experienced after configuring Jira with MySQL 8.0 or after upgrading MySQL to 8.0
- JIRA Deployment Fails with MySQL 4.1.x on Ubuntu
- Using an Unsupported Version of MySQL
This page refers to Portfolio classic plans. If you are currently running Portfolio 2.0, please check this link to access the latest page version.
When exporting backlog and release details to a CSV file, you get:
- an importable text file that contains all of the table information from your backlog and release tabs
- detailed information for issues in your backlog, including descriptions, dependencies, and estimates.
To export to a CSV file:
- Open your plan and go to Backlog.
- Select
. - Select a file location to save.
Last modified on Nov 5, 2018
Related content
- JIRA Cannot Create Issues when Using MySQL with Binary Logging
- Confluence will not start using MySQL 5.1.5+ with STATEMENT binary logging
- MySQL Binary Logging Problem with InnoDB When Creating a Workflow
- Bitbucket Server 2.7 fails to start with MySQL when binary logging is enabled
- Operations in Jira server fail with communications link failure in logs with MySQL
- Jira throws "Could not determine database type Unknown storage engine InnoDB" when starting
- "Communications link failure" Error with JIRA User Management on MySQL
- Various issues are experienced after configuring Jira with MySQL 8.0 or after upgrading MySQL to 8.0
- JIRA Deployment Fails with MySQL 4.1.x on Ubuntu
- Using an Unsupported Version of MySQL
Powered by Confluence and Scroll Viewport.