another change xxxx
Here are some ways Linear customers have approached moving issues from their previous tool to Linear.
We now have a migration assistant built into Linear that quickly copies over issues from GitHub, Jira, Clubhouse or Asana into Linear. Try t in Settings or learn more.
Three popular approaches
- Teams with smaller backlogs often prefer to transfer issues over manually. If you do this, the switch to Linear becomes an opportunity to review and cull their existing backlog.
- Teams with larger backlogs sometimes keep an active account on their old issue tracker and use it as a temporary backlog. If you do this, you can move issues over every week until you're ready to close the old account.
- To move over all issues quickly, you can use our importer. this option requires some coding expertise. Find documentation and a link to the importer here:
Importing issues. It's open-source and we welcome improvements. Contact us at hello@ if you create a pull request so we know to review it.
"We decided to manually move issues over to Linear. To be honest, we appreciated the chance to review the backlog and only put in issues that we planned to work on next. The manual migration of issues to Linear gave us the opportunity to decide on how we should be labelling issues, naming cycles, and using projects." - Oliver Shaw, Jasper
Tips to help your team adjust to Linear
- Share the
Onboarding tutorials and videos with your teammates and point to other resources such as the Linear Guide and Linear Method.
- Customize the workspace before inviting your full team onto it: add workflow statuses, labels and projects that already exist in your current process.
- Make sure you've set up the
Slack integration so that all teams can see updates in dedicated channels and configure their own personal Slack notifications.
- Import your team's custom Slack emoji so they can use them in Linear. This makes Linear more fun and maps to the existing ways your team communicates.