Import a Jira project
into Noots.
Connect with your Atlassian account email and an API token, pick a project, and Noots reads it through Jira's REST API and builds the project here. Nothing is written back to Jira and nothing keeps syncing afterwards.
How a Jira import runs.
Nothing is written back, nothing keeps syncing, and your credentials are not kept.
Connect
Paste the credential the import wizard asks for. It is used for that request and discarded.
Pick
A Jira project. Noots lists the first hundred projects your account can see, by name.
Import
One column per status name that actually appears on the issues it read, created in the order the issues arrive. It is the statuses in use, not the Jira board's own column layout.
Mapped, field by field.
- The issue key and summary become the task title, as PROJ-123: Summary.
- The description comes across as plain text. Jira stores it as a rich document, and the importer flattens it: links become their label text, and lists, headings, code blocks, tables and panels leave nothing behind.
- The priority is mapped onto low, medium or high by reading the priority's name.
Completion follows the column, not a flag. A card arrives in a column named after the one it was in, and it counts as complete only when that name is one this product already treats as done.
Left behind, on purpose and in full.
- Assignee and reporter
- Due dates, start dates and any date field
- Labels, components and fix versions
- Epic links, parent links and subtasks
- Story points and any estimate
- Sprints and boards
- Attachments, comments, worklogs and watchers
- Every custom field
- The issue type, the resolution and the link back to Jira
If one of these is the thing you cannot lose, export a CSV and use the paste importer instead. It is on every plan and it maps an assignee and a due date, which the live importer does not.
The ceilings a big workspace will meet.
Measured from the importer itself rather than estimated. A migration that quietly stops at a limit is worse than one that tells you the limit first.
- Up to two thousand five hundred issues per project, newest first. A larger project is cut off at that point without a warning on screen.
- The project picker shows a hundred projects in one page and does not paginate.
- Done and closed issues are imported like any other, and get their own columns.
- An import is a one-off copy, not a running sync. Nothing is written back to the source, and running the same import twice creates a second project with the same tasks in it.
- Your credentials are never stored. They travel with the request, make the calls and are discarded; there is no token table behind this.
- There is no undo. If an import is wrong, delete the project it made and run it again.
- Every import writes an audit row: which source, how many columns, how many tasks, who ran it and whether it finished cleanly.
- The person who runs the import becomes a manager on the new project, and the project takes your organisation's default visibility.
Moving from Jira.
Does it keep syncing with Jira?
What happens to formatting in descriptions?
Is my API token stored?
Start on the free tier.
Import into a free workspace first and look at the result before anybody pays for anything.
No card for the free tier. 10 people and 10 projects.