# Import from your issue tracker

Bring existing Jira work into a plan, refine it with the agent, and push it back to the same issues.



Work that already lives in Jira does not have to start over. Bring an epic or an issue into a plan,
refine it here, and push it back to the issues you started from.

## How to start one [#how-to-start-one]

Type it in the plan's chat:

```
import SIT-42
```

A Jira link works the same way, and `/import` in the composer fills the sentence in for you. There
is no separate import screen: the preview arrives as a card in the conversation, so what you brought
over stays in the chat history with the rest of the plan's story.

You can also just say what you want. If you tell the agent "we already planned the payments work in
Jira", it can find the item and offer the same card.

<Callout>
  Connect Jira in **Settings → Connectors** first. The same connection powers both directions, so if
  you can push to Jira you can import from it.
</Callout>

## What comes over [#what-comes-over]

The card shows the whole tree before anything is written:

* The item you picked **becomes the epic**, and its issues become specs.
* Sub-tasks **nest under their spec** as child specs.
* "Blocks" links become **needs-first** dependencies between specs.
* Images and attachments come along and land beside the specs that reference them. Pictures show up
  in the spec, and the planning agent can read them, so you can ask about a screenshot.
* The **comment thread comes too**, under a "Comments from Jira" heading, with the images people
  posted in it.
* Descriptions arrive **word for word**. Nothing is rewritten on the way in.

One issue with nothing under it lands as a single spec. If the structure is not what you want, the
top row has a toggle: bring it in as an epic with its specs, or as one spec with child specs. The
card re-counts as you flip it, so you can see what you are about to get.

## Choosing what to bring [#choosing-what-to-bring]

Untick anything you do not want. Unticking a parent leaves out everything under it, and there is a
one-click way to drop everything already marked Done, which is usually what you want when the epic
has been running for a while.

If you leave out a spec that another one needs first, the card says so and lets you continue. The
dependency becomes a note in the spec body instead of a broken link.

Nothing is written in Plansmith or in Jira until you press the button. Skipped items are remembered,
so bringing more over later does not ask about them again.

## After it lands [#after-it-lands]

The specs read exactly as Jira had them, which is the point: you can see what your team actually
wrote. When you want them in Plansmith's spec format, ask the agent to reshape them. It will do one
first so you can judge the result before it touches the rest.

If you then polish the epic and its jobs no longer line up with the imported specs, ask for a
coverage pass. The agent walks each job, says which specs cover it, which are partial and which are
missing, and proposes changes one spec at a time. It never rewrites your team's specs to match the
epic on its own.

## Pushing back [#pushing-back]

Every imported spec stays linked to the issue it came from. Push the plan and those same issues are
updated in place: no duplicates, and no second epic. You can see the link in a spec's frontmatter as
`tracker_key`.

If you asked Plansmith to mark the issues as checked out, the label and its comment come off once
the work has gone back.

<Callout type="warn">
  Plansmith is where the plan gets written, so bring work over when this is where it is going to be
  worked on. If a teammate edits an imported issue in Jira while you refine it here, the next push
  stops and asks rather than overwriting them. See
  [What happens when someone else edited it](/docs/push-to-your-issue-tracker).
</Callout>

Images travel one way too. A picture that came over with an issue renders in the spec, and the
planning agent can look at it. Pushing back does not re-upload the file to Jira: the issue keeps the
attachments it already had, and the description Plansmith pushes links to the copy here, which opens
for anyone who can already read the plan.

An image past the size limit is not brought over at all. The spec keeps its caption, marked as not
imported, and the check-out card names the file. If a single import carries a lot of pictures, the
last few arrive without a written description, and the card tells you how many.

Jira is the first issue tracker you can import from. Linear and Radial remain push destinations for
now. See [Push to your issue tracker](/docs/push-to-your-issue-tracker).