Jira

Import issues, epics, labels, and users from a Jira CSV export.

Workspace managers start from Settings → Administration → Import & export → Import from Jira (/settings/import-export/jira). Background: Importing guidance.

Data included in the import

After Pulse reads the file it reports issues, workflow states, epics, labels, and users. Open issues keep their workflow states. Completed issues go to the archive (a parent or sub-issue of an active issue is not archived). Epics become Pulse projects only when an imported issue belongs to them.

Optional Jira credentials (hostname, email, API token) pull images and link each issue back to Jira. The token is encrypted and never shown again. Using the assistant does not change Jira.

Pulse applies a removable Migrated label.

What import method should I choose?

CSV only. Export all fields from Jira, then upload (size limit shown in the dropzone). Replace the file if Pulse blocks it with row errors.

Considerations before importing

Pick a top-level destination team. Sub-teams are listed as Sub-team of parent — imports go to a top-level team. You can Create new team; it is created when you upload.

Mapping Jira users

On Map users, only members of the destination team can be assigned imported work. For each Jira person: Map to existing, Create with email, or Do not import. Invited people stay unassigned until they join the team. A skipped name is kept in the imported description and comments.

Matching Jira IDs

Keep the original Jira issue IDs is available when the CSV is a single Jira project and the destination team has no issue keys yet. Multi-project files and teams that already have issues get new Pulse IDs.

Sub-teams

Imports land on a top-level team, not a sub-team. Create or choose a parent team, then move work later if you need a child team. See Sub-teams.

Running the import

Confirm migrating vs skipping counts, then Start import. Statuses include preparing, importing, needs attention, completed, partial, and failed. You can leave the page while it runs.

You can delete a finished import within 14 days. That removes issues, projects, main docs, and comments the import created. Labels and cycles it reused, people it invited, and work you created yourself are kept. Jira is not changed. This cannot be undone.

Delete imported data is on the import detail (/settings/import-export/history/{importId}). After 14 days the window expires. An import that never ran can be discarded without deleting Pulse issues; a team created for that import is kept unless you delete it yourself.