Skip to main content

Export to Jira

Export to Jira

One click turns your VibeMap plan into a Jira board — features become Epics, stories become Stories, acceptance criteria become checklists, and your schema becomes a Confluence page. · Optional

🔒 Not yet available. Jira export is in final testing and switched off for customers. The Export to Jira button doesn't appear in the app yet, so the steps below describe how it works once it's enabled — not something you can do today. This page will lose this banner when the integration goes live.

Use this when your team runs delivery in Jira and you want your VibeMap spec to land as real, trackable work instead of a document someone has to re-key by hand. Skip it if you hand off entirely through your IDE agent (MCP) and don't use a Jira board.

The mapping

VibeMap uses a fixed, predictable mapping between its artifacts and standard Jira / Confluence types:

VibeMapJira / Confluence
FeatureEpic (business value, complexity, and effort written into the description)
User storyStory under its feature's Epic (or the project's standard issue type, such as Task, when it has no Story type)
Acceptance criteriaChecklist (task list) inside the Story description
PriorityJira priority (High / Medium / Low)
Database schemaConfluence page (one section per table), linked from the Epics

Each exported issue carries a vibemap label, and story summaries follow the canonical "As a <role>, I want to <goal>" form (Jira caps summaries at 255 characters, so longer titles are truncated).

Connecting Atlassian

  1. Open Prepare for Dev and click Export to Jira (top right, next to the Prepare button). The same button is also on App Builder → Code Preview.
  2. Click Connect Atlassian and approve access for your Jira site. VibeMap requests Jira work and Confluence page scopes; your tokens are encrypted at rest and only ever used with your own account. When you come back, the dialog reopens on its own.

Export to Jira dialog Figure: Export to Jira dialog.

Exporting

  1. If your Atlassian account covers more than one Jira site, pick the Jira site first.
  2. Pick the destination Jira project (it must already exist). Use a Jira Software (Scrum or Kanban) project: it needs an Epic issue type, which business projects usually don't have.
  3. Pick the Confluence space for the schema page. Team (global) spaces are listed first, then personal spaces marked (personal). If you don't want a schema page, choose Don't publish schema to Confluence. The first time, nothing is pre-selected, so you have to choose. After that, VibeMap remembers your choice for this project and site.
  4. Click Export. The run happens in the background, so you can close the dialog — reopen it any time to see progress, the result, and a link to the project in Jira. Only one export of a project runs at a time.

Behind the scenes VibeMap creates the schema Confluence page first (so Epics can link to it), then creates an Epic per feature and a Story per user story, attaching acceptance criteria as a checklist on each Story.

💡 Tip: Re-exporting is safe. VibeMap remembers which Jira issue each feature and story maps to and updates them in place instead of creating duplicates. If you deleted an issue in Jira, the next export recreates it. Labels your team added in Jira are kept. The Confluence schema page is regenerated on every export, so edit your schema in VibeMap — not in Confluence.

Features and stories you deleted in VibeMap

If you delete a feature or story that was already exported, the next export doesn't delete its Jira issue. Instead it adds the label vibemap-removed to the issue and keeps all of its other labels. This happens once per issue, so exporting again doesn't add the label twice. The result tells you how many issues were labelled this time, for example "2 issues labelled removed". Deleting a feature also labels the Stories under it.

In Jira, search for labels = vibemap-removed to review these issues, then close or delete them yourself. If the feature or story comes back in VibeMap (for example, you restore an earlier version), the next export updates the same issue and removes the label.

Changing the Confluence space

If you pick a different space, the next export creates a new schema page in that space and links the Epics to it. The old page stays where it was. VibeMap never deletes Confluence pages. If the space you picked has been deleted, or you no longer have access to it, the dialog tells you and asks you to pick another space. If this happens during an export, your Jira issues still export and only the schema page is skipped.

If an export fails

The dialog says what went wrong and what to do. The common cases:

  • Connection expired or revoked — click Connect Atlassian again, then export.
  • No permission — your Atlassian account needs Create issues permission on the Jira project.
  • Jira is rate-limiting — VibeMap already waits and retries; if it still fails, export again in a few minutes.
  • A required field — if the Jira project requires a field VibeMap doesn't fill (for example Components), make it optional or export to another project.

Issues created before a failure are kept and linked, so exporting again picks up where it stopped.

Syncing status back from Jira

VibeMap can also listen for Jira status changes, so that a Story dragged into an In Progress column becomes In Progress in VibeMap and one dragged to Done completes. Jira's backlog/to-do states are left untouched.

⚡ Not self-serve yet. Status sync needs a webhook that VibeMap registers on your Jira site, so it isn't something you can switch on from the dialog. It covers user-story status only (Jira → VibeMap); epics, fields and comments are not synced.

⚡ Power-user hints

  • The export is idempotent by design: run it after each planning change and your board stays in step without a pile of duplicate Epics.
  • Priority only maps when your Jira project uses the default High / Medium / Low scheme and shows a Priority field. Otherwise issues are created without one, and you can set it on the board afterwards.

↔ The traditional way

A lead normally reads a PRD and hand-creates Epics, Stories, sub-tasks, and acceptance-criteria checklists one by one — hours of copy-paste that drifts out of date the moment the plan changes. VibeMap generates the whole hierarchy in one pass and re-syncs it in place, so the board is a live projection of the spec rather than a stale snapshot of it.

Notes and limits

  • Sites without Confluence still export fine — the schema page is simply skipped. If Confluence rejects the page, the Jira export still completes and the dialog tells you the page wasn't published.
  • The schema page goes into the Confluence space you pick, or nowhere if you choose Don't publish schema to Confluence. VibeMap remembers the space through the schema page it published. If your project has no schema tables yet, no page is published, so you'll be asked for a space again next time.
  • Deleting a feature or story in VibeMap never deletes its Jira issue. The issue is labelled vibemap-removed instead. If your Jira project has no Labels field, the dialog says how many issues couldn't be labelled.
  • Jira summary length is capped at 255 characters; longer story titles are truncated.
  • Custom priority schemes without High / Medium / Low leave issues without a priority.

What's next

We use cookies to understand how VibeMap is used and to improve it. If you decline, or until you choose, we only count visits anonymously, without storing anything on your device. See our privacy policy.