Moving from Jira
How to bring a Jira project into IT4S, what comes along and what doesn't. The import reads Jira Cloud over its API; you can run it as often as you like until you switch, and every run updates instead of adding twice.
Step by step
- Connect Jira: under Administration › Settings › Integrations, enter the Jira address, the email of an Atlassian account and its API token, Save, then Test Connection. The account must be able to see the projects you want to import.
- Choose the project: Administration › Jira Import, pick the Jira Project, then Import Into: A new project (IT4S creates it with the IT4S Project Key and name; issue keys keep the Jira key) or An existing project (its issues join the project's own; issue keys change to the project's key, also where texts mention them, and numbers that are taken get the next free one).
- Analyze: IT4S exports the project in the background and shows what the import would create: issues, comments, worklogs, attachments, releases, components, tags, people and the problems it found. Nothing is imported yet.
- Check the Status Map: every Jira status of the project with the IT4S status its issues get. Rows that only match by their Jira category have a warning; choose the right status there.
- Check the users: Jira people are matched by email (or by name), or by the user map you fill in. For Users without IT4S account, choose Create them as inactive users (when Jira shows their email; you can invite them later) or Attribute their issues and comments to the admin who imports.
- Import: issues, comments, worklogs, attachment files and the field history go in; the page shows the progress and, at the end, what was created and updated.
- Look at the result: the project's board, a few issues and their Activity tab. Then invite your team (see Administration).
- Until you switch: open the last run and click Refresh from Jira and Import. IT4S downloads the project again and updates what changed in Jira, also worklogs deleted there.
What comes along
| Jira | IT4S |
|---|---|
| Issue types Epic, Story, Task, Bug, Sub-task | the same types; New Feature becomes Story, Improvement and Spike become Task, other types Task (or Sub-task for sub-task types) |
| Statuses | by name (To Do, In Progress, In Review, Done, Won't Do and common variants), else by the Jira category; your choice in the Status Map wins. Done with a resolution like Won't Fix, Duplicate or Declined becomes Won't Do. In Planning, New Idea and Waiting for approval get the nearest status plus a tag with the original name |
| Priorities | Highest/Blocker/Critical → Highest, High/Major → High, Medium/Normal → Medium, Low/Minor → Low, Lowest/Trivial → Lowest |
| Summary, description, assignee, reporter, due date | the same fields; the reporter falls back to the creator |
| Parent and epic link | parent; a parent outside the export is dropped with a warning |
| Labels | tags |
| Fix versions | releases (released or not, with the release date); with several, the issue keeps the first |
| Components | components with a short code; with several, the issue keeps the first and a comment names the others |
| Original and remaining estimate | estimates in time |
| Comments, worklogs, attachments | comments, worklogs (with author and day), files on the issue |
| Issue links | blocks, relates to, duplicates; clones and unknown link types become relates to |
| Board order (rank) | the order on the IT4S board |
| History | the Activity tab shows changes of status, assignee, priority, type, title, tags, release and parent with Jira's date and author, marked via Jira import |
| Links to other Jira issues in texts | open the imported issue in IT4S (also board links with selectedIssue=…) |
What stays in Jira
- Custom fields, story points, resolutions as a field, sprints, Jira workflows and schemes, boards and filters, dashboards and Marketplace app data.
- Changes of fields IT4S doesn't have are skipped in the history; the result says how many.
- Links to issues that weren't imported, and Confluence links, stay as they are; the Attachments in Jira line keeps pointing to Jira. Confluence pages come over with the separate Confluence import into the documentation.
Good to know
- Run it again any time: issues by key, comments, worklogs and files by their Jira id, releases and tags by name: nothing is added twice, and changes in Jira update IT4S.
- Plan limits apply: on Free a workspace has up to 3 projects and 3 users; people the import creates as inactive users don't count until you invite them. Large imports with many files need the storage of the Team plan.
- The time it takes depends on the number of issues, comments and files; the page shows the progress and keeps running when you close it.
- Help with the move: Silvertip moves bigger setups with you (more projects, Confluence, people and roles): write to info@silvertip-it.at.