Import and Export with Jira

If your requirements start life in Jira, or your analysts want the finished set back there, the requirements editor connects both directions. The exchange is always explicit: nothing moves without a button press, and you see exactly what will be created before it happens.

Plan Availability

Requirements integration is available on the Medium plan and above, with a Jira connection configured in Settings → Integrations.

Import an Epic

1. In the requirements editor, choose Import from Jira.
2. Pick the epic; its child stories are read through your connection.
3. The stories arrive as draft requirements: review each, keep what belongs, edit phrasing for the traceability rules, and discard the rest.

Importing never modifies anything in Jira; it is a read.

Export the Requirements

1. Choose Export to Jira and pick the target project.
2. The export modal shows precisely what will be created: one epic for the package with a story per requirement.
3. Confirm, and the items are created through your connection, ready for backlog work.

This Is an Exchange, Not a Live Sync

Requirements do not sync continuously in either direction; each import or export is a deliberate act. If the Jira side changes after an import, re-import and re-review. (Delivery items are different: after a delivery plan export, status does sync back on a schedule.)