Skip to content

Import from Jira Cloud

You will learn how to connect Jira Cloud, run the one-shot project import wizard, reconcile users, and open the new Tixio project.

Only workspace owners and admins can connect Jira or run imports. The wizard creates a new Tixio project; it does not merge into an existing project or keep a live sync after import.

1. Connect Jira Cloud

  1. Open Settings > Integrations > Jira Cloud.
  2. Enter:
  3. Site URL — your Atlassian site (for example https://your-company.atlassian.net).
  4. Account email — the Atlassian account that will call the API.
  5. API token — create one from Atlassian account settings.
  6. Enable Enable Jira connection.
  7. Choose Save connection, then Test connection.

A successful test shows Connection OK. If validation fails, read Last validation error and fix the site URL, email, or token.

Choose Disconnect later if you need to remove the connection.

2. Start the import wizard

From the Jira Cloud page, choose Import a Jira project, or open the import route from that settings area.

Pick a project

  1. Under Choose Jira project, select a project.
  2. Choose Start import.

Tixio discovers Jira metadata (statuses, issue types, custom fields, and related entities) before mapping.

Map into Tixio

  1. Review the Target project name, short name, and description.
  2. Map Status mapping — each Jira status to a Tixio label and category (backlog, unstarted, started, paused, completed, cancelled).
  3. Map Issue type mapping — Task, Story, Bug, Epic, Subtask, Initiative, and related types as offered.
  4. Map Custom field mapping when needed. Options include short text, number, date, single select, and user. Choose Don't import to skip a field; unmapped fields can land in the issue description under a Jira fields heading.
  5. Choose Save mapping, then Preview import.

Multi-value custom fields are not supported for native mapping in this wizard.

Preview and reconcile

The preview shows whether the import is Ready or Not ready, with counts for issues, epics, labels, sprints, comments, attachments, links, and optional initiatives or saved views from Jira boards.

If the preview lists workspace groups, decide whether to create new groups or merge into existing ones.

Under Reconcile users, for each Jira user choose:

  • Import stub, or
  • Map to member and pick an existing workspace member.

Unresolved users block commit until you finish reconciliation.

Commit

  1. Choose Start import when the preview is ready and reconciliation is complete.
  2. Watch live progress (for example importing issues or fetching comments).
  3. When you see Import complete, choose Open project.

You can Cancel an in-progress job from the job header. A failed import does not leave a partial project.

What comes across

Typical imports include:

  • Issues with comments, attachments, and issue links.
  • Epics and, when present, initiatives that group epics.
  • Versions mapped into Tixio versions.
  • Sprint history where available.
  • Saved views created from Jira board names.
  • Groups derived from Jira permission or role groups when the wizard offers them.

Imported Jira keys remain searchable in Tixio (command search and MCP), so old keys such as OLD-42 still resolve after import.

Limits to expect

  • Jira Cloud only; API token auth (not OAuth) in this flow.
  • One-shot into a new project — not incremental sync.
  • Owners and admins only.
  • Commit is all-or-nothing for the import job.

Next