Use this route to move Jira work items into a ProductLift feedback board. If your developers will keep working in Jira, consider the Jira integration instead.
The all-fields export includes comments in separate Comment columns. Attachment URLs are not the attachment files. These steps are for Jira Cloud; see Atlassian's export guide.
| Source data | ProductLift field |
|---|---|
| Summary | Title |
| Description | Description |
| Status | Status |
| Issue key | Jira Key |
| Labels / Components | Tags, combined into one comma-separated field |
| Reporter email | Author Email |
| Assignee email | Assigned To |
| Created | Created Date |
| Due date | Estimated Date |
| Fix version | Version or Release |
Use real email addresses for people, not Jira account IDs or display names. Match assignees to ProductLift team members. If repeated Labels or Components columns appear, combine their values before importing.
Priority is not a vote count. Keep it as context or review how it fits your ProductLift prioritization method. Do not turn a High priority value into invented customer votes.
Comment columns need a separate import through the API. Do not append internal Jira conversations to a public post description. Check issue restrictions and attachments before choosing a public destination.
Compare the export row count with the items you selected. If the export is incomplete, split it into non-overlapping date ranges or use Jira's API. The ProductLift importer accepts CSV or Excel, not a Jira JSON response.
The post import guide covers supported fields and finding an import batch. For changing your domain, widgets and customer login after the move, follow the migration checklist.