Purpose

Migrate BugNet issues to Jira. Because there is no migration tool to automate this, the process will have to be done manually by following Importing Data from CSV

Overview:

BugNet issues will have to be extracted and formatted into a CSV file with the following format:

Assignee, Summary, Description, Attachment, Comment, Comment
Admin, "Issue demonstrating the CSV attachment import", "Please check the attached image below.", "https://jira-server:8080/secure/attachment/image-name.png", "01/01/2012 10:10;Admin; This comment works",
Admin, "CSV attachment import with timestamp,author and filename", "Please check the attached image below.", "01/01/2012 13:10;Admin;image.png;file://image-name.png", "01/01/2012 10:10;Admin; This comment works","02/01/2012 10:10;Admin; And a second comment"

Atlassian Cloud no longer supports importing users.

issues.csv will be imported using the Jira Importer and may contain more columns to add more content to issues as described in Importing Data from CSV.

Projects, Users, Groups, Roles, Permissions, Status, Priority, Type, Resolution won't be imported and will have to be manually recreated.

Solution

1. Export BugNet to Excel

2. Create a issues.csv file by following the format guidelines described at Importing Data from CSV.
   Note that : 
   1. Multiple Comments require the same header name
   2. For issues that have less comments, the cell must be left empty
   3. Comments and Attachments format is surrounded by quotes: ". To specify: Date, User, file or comment. They should have quotes in Excel and look like the example when saved as CSV and opened on a simple text editor.
   4. Date format can be specified during the import but all date formats in the file must match. Excel allows changes in date format very easily.
   5. Spaces in filenames can be replaced by %20 in the CSV or renamed with underscore: Unable to import file attachment from CSV
3. Advanced formatting of issues.csv:
   1. Attachments:
      Many attachments can be imported by using multiple columns named "Attachment"
      There are 2 alternatives to locating the attachments so they can be grabbed by the CSV importer:
      1. Public server: Attachments will be accessible at their URL. e.g: https://mypublicserver.company.com/attachments/image-name.png
      2. Upload them to WebDav and ask Cloud Support to move them to the jira/home/import/attachments directory: Attachments will be accessible at: file://image-name.png
         Files can be grouped in Folders in which case they will be accessible at: file://folderName/image-name.png
   2. Statuses, Priorities, Issue Types, Resolutions: some of these may be missing in the Jira installation you are importing to. If so, manually create them and import again.
   3. HTML Tags: Because BugNet Summary is saved in HTML format, it will be displayed with HTML tags in Jira. There are different alternatives to replacing HTML tags, (see this stackoverflow post)
      You could use "Find and Replace" on a text editor to manually strip HTML tags or replace them:
      1. <p> and <br> replace for an Enter
      2. <li> replace for a * as it will then create lists of the items
      3. after replacing those, replace all others <*> with empty string to remove them.
   4. The export might carry non-ascii character. You can remove them by following this stackoverflow solution
4. Do a quick test with a couple of issues by following Importing Data from CSV and save the Configuration of the import for future imports.
5. After solving all the problems and clearing all doubts, you can remove tests projects and do the final import.

All the best!