Import from Jira

The Jira importer migrates your Jira projects, issues, statuses, priorities, assignees, labels, and comments into SetGet. The importer connects to Jira Cloud via API, lets you select a project, maps Jira fields to SetGet fields, and runs the import with real-time progress tracking.

What gets imported

Jira field	SetGet field	Notes
Project	Project	A new SetGet project is created (or you can import into an existing one)
Issue summary	Work item title	Direct mapping
Issue description	Work item description	Converted from Jira markup to SetGet editor format
Status	State	Mapped via the status-to-state table
Priority	Priority	Mapped via the priority table
Assignee	Assignee	Matched by email address
Labels	Labels	Created in SetGet if they do not exist
Comments	Comments	Imported with author attribution
Attachments	File assets	Re-uploaded to SetGet storage
Epic	Label or Module	Configurable during mapping
Sprint	Cycle	Optional -- map Jira sprints to SetGet cycles
Story points	Estimate	Mapped to SetGet estimate field
Sub-tasks	Sub-work-items	Preserved as child items
Issue links	Relations	Mapped to SetGet work item relations

Prerequisites

• A Jira Cloud instance (Jira Server and Data Center are supported via API token).
• A Jira account with read access to the project you want to import.
• Admin or Owner role in your SetGet workspace.

Setup steps

Step 1 -- Connect to Jira

1. In SetGet, go to Settings > Import.
2. Select Jira from the list of importers.
3. Enter your Jira instance URL (e.g., https://yourcompany.atlassian.net).
4. Enter your Jira email address and API token.
   • Generate an API token at id.atlassian.com/manage-profile/security/api-tokens.
5. Click Connect.
6. SetGet validates the credentials and shows a green "Connected" status.

TIP

Use a Jira account that has read access to all the projects you plan to import. A service account is ideal for this purpose.

Step 2 -- Select the Jira project

1. After connecting, SetGet lists all projects accessible from the Jira account.
2. Select the project you want to import.
3. SetGet scans the project and displays a summary: issue count, status count, labels, sprints.

Step 3 -- Choose the target project

• Create new project -- SetGet creates a new project with the Jira project name and key.
• Import into existing project -- select an existing SetGet project. Imported work items are added alongside existing ones.

Step 4 -- Map statuses to states

Jira statuses must be mapped to SetGet workflow states. The importer suggests default mappings based on status categories.

Jira status category	Suggested SetGet state group
To Do	Backlog or Unstarted
In Progress	Started
Done	Completed

For each individual Jira status, select the corresponding SetGet state:

Jira status	SetGet state (example)
Open	Backlog
To Do	Todo
In Progress	In Progress
In Review	In Review
Done	Done
Closed	Done
Won't Do	Cancelled

If a SetGet state does not exist yet, you can create it directly from the mapping interface.

Step 5 -- Map priorities

Jira priority	SetGet priority
Highest	Urgent
High	High
Medium	Medium
Low	Low
Lowest	None

Adjust mappings as needed.

Step 6 -- Configure additional mappings

Option	Description	Default
Import comments	Bring over all issue comments	On
Import attachments	Re-upload file attachments to SetGet storage	On
Import sprints as cycles	Map Jira sprints to SetGet cycles	Off
Import epics as modules	Map Jira epics to SetGet modules	Off
Import epics as labels	Map Jira epics to SetGet labels	On
Import sub-tasks	Import sub-tasks as child work items	On
Import issue links	Map Jira issue links to SetGet relations	On

Step 7 -- Review and start import

1. Review the mapping summary.
2. Click Start Import.
3. The progress screen shows:
   • Total issues to import
   • Issues imported so far
   • Current item being processed
   • Estimated time remaining
   • Errors (if any)

WARNING

Do not close the browser tab during import. While the import runs server-side, the progress UI requires an active connection.

Post-import validation

After the import completes:

Check counts

Metric	Where to check
Total work items	Project > All Work Items view
By state	Project > Board view (count per column)
By priority	Project > Analytics > Priority Distribution
Labels	Project > Settings > Labels
Cycles	Project > Cycles

Spot-check items

• Open 5-10 work items and verify title, description, state, priority, and assignee.
• Check that comments appear in the correct order with correct attribution.
• Verify attachments are accessible.

Resolve mapping issues

If some items have incorrect states or priorities, you can:

1. Update the items manually.
2. Use bulk edit to change multiple items at once.
3. Re-run the import with corrected mappings (but note this creates duplicates -- delete the first batch first).

Handling duplicates

The importer tracks Jira issue keys to avoid duplicates during a single import run. However, running the importer a second time for the same project will create duplicate work items. If you need to re-import:

1. Delete the work items from the first import.
2. Re-run the import with updated mappings.

Troubleshooting

Problem	Cause	Solution
Connection failed	Wrong credentials	Verify Jira URL, email, and API token
No projects listed	Insufficient permissions	Use an account with project read access
Import stuck	Large project with many attachments	Wait longer; attachment upload is slow
Descriptions look broken	Jira markup not converting	Report the specific markup pattern for a fix
Assignees not mapped	Email mismatch	Invite the member to SetGet with the same email
Sprints missing	Sprint import disabled	Enable "Import sprints as cycles"

TIP

For very large Jira projects (10,000+ issues), consider importing in batches by using JQL filters to select subsets of issues.

Related pages

• Import and export overview
• Import from GitHub
• Import from Linear
• Import from CSV
• Workflow states
• Export data