Switch
Switching from Jira to TManage
What TManage brings over from your export, and what to check before you start.
It may be time to move if…
- Your team delivers projects for clients, not only releases
- Clients need to follow progress and approve work in a portal of their own
- You track time and bill clients for it
TManage may suit you if…
- Clients approve your work and you want a record of it
- You work in Arabic and English
- You want tasks, time and invoices in one place
What comes over
| From Jira | In TManage |
|---|---|
| Issues and their keys | Work items that keep their keys (WEB-42 stays WEB-42) |
| Epics | A label on each of their issues |
| Statuses | Work states, matched by name |
| Assignees | Owners, matched to members of your team. Anyone not matched comes over unassigned |
| Sprints | Iterations |
| Due dates | Due dates |
| Priority | Priority |
| Descriptions | The work item’s description |
Jira is a trademark of its owner. TManage is not affiliated with it.
How the move works
TManage’s importer reads a Jira issue export in CSV, one Jira project per file. On the Import page, choose Jira, pick the project the issues go into and check how the columns match. Every row is checked before anything is saved, and one file holds up to 1,000 rows.
Changed your mind?
Any import can be undone in one click for 7 days. Work whose owner does not match a member of your team comes over unassigned, so you can assign it afterwards.
Files and attachments
Attachments are not copied over. Your files can stay in your own Google Drive or OneDrive.
See it with your own projects
Free during the beta · No card needed · Client users always free