Projects & issues
Importing from Jira
Connect Jira Cloud with an API token and bring over projects with their issues, statuses, sub-tasks, story points, links and comments.
Moving from Jira? Connect your Jira Cloud site with an API token and Deckbell copies your projects and issues straight from Jira.
You need permission to manage issues to import, and permission to create projects to import into new boards. Jira Server and Data Center aren't supported; export a CSV from them instead.
Get a Jira API token
- Go to your Atlassian account's Security → API tokens page (id.atlassian.com).
- Click Create API token, name it (for example Deckbell import) and copy the token.
- Note your Jira address, such as
your-company.atlassian.net, and the email address you sign in to Atlassian with.
Deckbell only uses the token while the import runs and deletes it when the import ends. You can revoke it in your Atlassian account afterwards.
Start an import
Start from Settings → Import → Jira, or from a board's ⋯ → Import issues → Jira to import into that board.
- Enter your Jira site, email and API token, then click Connect to Jira.
- Tick the projects to import.
- Choose a new board for each project, or an existing board.
- Choose whether to import comments.
- Click Next, check the statuses, and click Import.
When importing into an existing board, each Jira status is matched to a column with the same name, or one of the same kind. Change any of them, choose Create a matching column, or Don't import. New boards get one column for each Jira status: To Do statuses become to-do columns (names like Backlog become backlog), In Progress statuses become in-progress columns, and Done statuses become done (or canceled, for names like Won't Do or Declined).
What gets imported
| From Jira | In Deckbell |
|---|---|
| Summary and description | The title and description. Jira formatting (headings, lists, tables, code, links, mentions) becomes Markdown. |
| Status | The column you chose. Resolved issues keep their resolution date. |
| Priority | Highest, High, Medium, Low and Lowest become Urgent, High, Medium and Low. |
| Story points | The estimate, when your site has a Story Points or Story point estimate field. |
| Assignee and reporter | Matched to teammates by email address, then by display name. |
| Labels | Created on the board when missing. |
| Sub-tasks and parents | Stay under their parent issue. |
| Issue links | Blocks links keep their direction; other link types become related. |
| Comments | Up to 200 per issue, with their original date and author. |
| Created date | Kept; issues are numbered in creation order. |
Each issue shows Imported from Jira · WEB-123, linked to the original.
Good to know
- Some Jira sites hide people's email addresses. Deckbell then matches assignees and comment authors by display name, so make sure teammates use the same name in Deckbell.
- Attachments aren't copied; images in descriptions show as (attachment not imported).
- Importing again skips issues that were already imported and fills the same boards.
- One import brings over up to 10,000 issues, and your plan's issue and project limits apply. See Plans & billing.
- Large projects take a while because Jira limits how fast it can be read. You can close the dialog; progress is shown under Settings → Import.