Import Jira Work into Plane with Explicit Mapping Checks
Use Plane Workspace settings > Imports and choose the Jira connector matching Cloud or Server/Data Center. Map states and priorities before confirming the import.
The Jira importer is documented for Plane Cloud and all self-hosted Commercial Edition plans. The Jira account must read the selected project and its issue metadata. Preserve the source until the migration is verified.
Example: migrate a small Billing issue subset with a JQL filter first, including a subtask, custom property and comment, before importing the remaining project.
Step-by-step guide
Prepare the target and credentials
Create or choose the Plane project. Enable Work Item Types beforehand if issue types need to become Plane types on an eligible plan. Prepare the Jira token, account email and site URL.
Connect and bound the source
Open Workspace settings > Imports and the correct Jira connector. Connect the credentials, select the target Plane project and source Jira project, then use an optional JQL filter for a representative sample.
Review people and mappings
For Jira Cloud, upload the user CSV or explicitly skip user import. Map states and priorities. Skipping users leaves assignees empty and attributes work/comments to the migration runner.
Confirm and reconcile imported work
Review Summary and click Confirm. After the background import completes, inspect titles, hierarchy, original Jira links, comments and ownership against the sample before expanding scope.
Common mistakes
Assuming Jira types always migrate
Without enabled Work Item Types, issues import but Jira issue types are not created as Plane work-item types.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.