Import from Jira in 60 seconds

The fastest way to evaluate sprintrr with your real data — without re-typing a single issue.

1

Connect your Jira workspace

Open Settings → Jira integration. Paste your Jira Cloud URL (https://yourcompany.atlassian.net) and your Atlassian email.

Generate an API token at id.atlassian.com/manage-profile/security/api-tokens: click Create API token, name it (e.g. “sprintrr”), set an expiry (default 1 year, max 365 days as of Dec 2024), and copy the token immediately — Atlassian shows it only once.

We validate the credentials by calling /rest/api/3/myself before storing the token. If Atlassian rejects them, you'll see the exact error inline instead of a vague failure later.

2

Pick a Jira project + preview the mapping

The wizard lists your accessible Jira projects, lets you pick one, and shows the top 25 issues with the proposed sprintrr mapping per row — status, priority, category, due date, assignee (matched by email when the user exists in your team), and epic → milestone (matched by title).

3

Import — up to 100 issues per run, idempotent

Click Run. Existing tasks (matched by Jira issue key) are updated; new tasks are created. The hard cap is 200 in v1; for larger projects, split them with a JQL filter in the next pass.

4

Use the rest of sprintrr

Imported tasks carry an “Imported from Jira” badge with a deep-link back. From here the full sprintrr toolkit works: status updates, transcripts → tasks, risk register, date-cascade replanning, MCP for Claude Desktop / Cursor.

Security & data posture

  • API token encrypted with AES-256-GCM via BYOK_ENCRYPTION_KEY at rest. Token never leaves the server decrypted.
  • One-way only. sprintrr never writes back to Jira. Your source of truth in Jira stays untouched.
  • Disconnect at any time — Settings → Jira integration → Disconnect drops the encrypted token row.
  • Audit-logged. Connect, disconnect, and every import action emits an audit log entry.
  • RLS-scoped. Integration rows and import job history are visible only to the owning user.

What gets mapped

Jira→ sprintrr
summarytitle
description (ADF)description (flattened to plain text)
status (via statusCategory)Not Started / In Progress / Completed / Blocked
priorityHigh / Medium / Low (sensible defaults)
issuetypecategory (Story → Development, Bug → Testing, etc.)
assignee.emailAddressassigned_to[] (matched to team members by email)
duedatedue_date
parent (epic) summarymilestone (matched by title — existing only, never auto-creates)
key + browse URLexternal_id + external_url (badge + deep-link)