Moving from Jira
Bring your Jira projects with you
Zicket imports a Jira Cloud project over Jira’s API, with nothing silently dropped. Your team keeps its issue keys and history, and your agents can start on the imported tickets straight away.
What comes across
- ✓Issue keys, so PROJ-123 stays PROJ-123
- ✓Original created and updated dates
- ✓Original authors, as Zicket members or as named people from Jira
- ✓Epics, stories, tasks, bugs and subtasks, with their hierarchy
- ✓Statuses, mapped to workflow states in your board’s column order
- ✓Labels, comments and attachments
- ✓Issue links
- ✓The change history
- ✓Sprints, versions, components and other Jira fields, kept read-only on each issue
How it works
- 1
Connect your Jira Cloud site
In Zicket, open Imports and connect with your Atlassian account email and an API token. - 2
Pick a project and check the mappings
Zicket proposes how Jira statuses, issue types and people map onto Zicket. Review and change them before anything runs. - 3
Run the import
It runs in the background and survives restarts, so you do not need to watch it. The new project is read-only until you finish, so nothing gets out of step. - 4
Re-run if Jira changed, then finish
A re-run updates what changed, safely. When you are happy, choose Finish import and the project opens for everyone.
Good to know
- Jira Cloud is supported. Jira Server and Data Center are not.
- Each Jira project becomes a new Zicket project, keyed by its Jira key.
- It is a one-way move: changes in Jira after you finish are not synced.
- Comparing first? See Zicket vs Jira.