A set of helper tools for importing issues from a classic Jira project into a next-gen project. This application is meant to be used in conjunction with the JIRA's built-in CSV issue importer. Currently, that tool causes several bugs:
- All issue types are forced to type 'Story' or 'Task' (See bug)
- Story points are removed
- Epics lose their children
- Sub-tasks lose their parent relationships
- Split issue relationships are lost
- Component info is lost
- Version status and resolution dates are lost
This project will:
- Set issues to their correct type
- Add story points
- Set Epics as Story type and create "Relates" issue type relationship with former children
- Currently there is not way to convert a Task to Epic
- Add sub-tasks to their correct parent tasks
- Add components as ticket labels (Next-gen does not support components)
- Migrate versions status and resolution dates
# Install dependencies with Go Modules
$ go mod init
# Generate a local configuration file
$ cp .env-example .env
- Issues & Filters > All Issues > Advanced Search > Export > Export Excel CSV (all fields)
- If project has more than 1000 issues, follow instructions here to paginate
- Edit the Permission Scheme for the project (if migrating between Jira Cloud Instances)
- Set 'Browse Projects' permission group to 'Public'
- This allows the importer to migrate attachments
- Edit the exported CSV file
- Change
Created
,Updated
,Last Viewed
andResolved
columns to date formatdd/MMM/yy h:mm am/pm
- Change
- Project Settings > Issue Types
- Create additional issue types to match types in the classic project
- Jira Settings > External System Import > CSV
- Upload the CSV and configuration file (optional)
- Map CSV fields to Jira fields
- Check 'Map field value' for Status to confirm they are migrated correctly
- Run the import
$ go run cmd/importer/main.go ./path-to-csv