Jira sync

Jira stays your source of truth.

Rundown reads the projects, issues, sprints and worklogs you already trust, on a schedule you set, and only what changed. When a plan is ready, the sync runs the other way too: estimates, assignees and sprints go back to Jira.

How it works

From a Jira site to live numbers

Four steps, and you decide what comes across before anything does.

  1. Step 1

    Connect your Jira site

    Sign in with Atlassian and approve access. No API tokens to paste, and the permissions you set in Jira carry across.

  2. Step 2

    Scan before anything moves

    Rundown lists every project on the site with its issue count and last activity, so you see what is there before a single issue is copied.

  3. Step 3

    Choose the scope

    Pick projects, people and how far back to go, or sync everything in one click. Either way you see how many issues and roughly how long it takes.

  4. Step 4

    Sync, and see what came across

    Every run reports what was added, updated and left unchanged, and names anything that failed, so a quiet sync is never a silent one.

Scope and schedule

Years of Jira, without the wait

Bring in what you need, keep it fresh on its own, and narrow it again whenever you like.

Scope

Sync exactly what you need

Ten years of Jira does not have to come across in one go. Decide which projects, which people and how much history Rundown brings in. Change it whenever you like.

  • Pick projects and people
    Rundown scans your Jira site first and shows every project with its issue count and last activity. Tick the ones you need; long-dormant projects are hidden.
  • Choose how far back
    Bring in the last few months or years, and leave untouched backlog tickets out. Completed work always comes along, so velocity and burndown stay right.
  • Know before you sync
    See how many issues are in scope and roughly how long the sync will take before you start it.
  • Narrow it safely
    Take a project out of scope and Rundown can clear out the data you no longer need. Hours already logged against it are always kept.
Schedule

Fresh data without lifting a finger

Set a schedule once and Rundown keeps itself up to date on its own, so plans, budgets and reports are current when your team starts work.

  • On your cadence
    Every day, every few days or once a month, at the hour you choose, in your workspace’s own timezone.
  • Only what changed
    Each run picks up where the last one stopped, project by project, so a scheduled sync stays quick even on a large site.
  • New projects included
    Projects created in Jira later can join your scope automatically, or Rundown tells you they appeared so you decide.
  • Manual sync any time
    A schedule never locks you out: start a sync by hand whenever you need the latest data right now.
And back again

Your plan, written back to Jira.

Plan the sprint in Rundown and Sync to Jira lists every difference, side by side: what Jira says now and what you planned. Tick what should change and apply it, column by column.

  • Planned hours become the original estimate
  • The planned person becomes the assignee
  • Issues move into the sprint they are planned in
  • Nothing is written until you apply

Connect Jira and see your numbers today.

Connect your Jira Cloud site, choose what to sync, and plans, budgets and reports fill in on their own. Free for 60 days, no credit card required.