Create teams in your workspace to organize members who regularly work together such as design, engineering, and marketing.
By default, when you create a workspace we'll generate a team for you with the same name. It's up to you how to split up teams and you can be part of one or many teams. Here are different ways you can:
- To group teammates who work together frequently.
- To group an area of work such as marketing, mobile app, etc.
- On small teams, it can help to keep everyone together to get the most out of features such as cycles.
- When first trying out Linear it can help to start with one team to keep things simple as you learn how features work.
O then T to open teams
Ctrl Shift 1-9 to go to a specific team
G then S to go to settings to configure team settings, create teams, or delete teams
Cmd/Ctrl Shift M to move issues to a new team
Create teams under workspace settings by clicking the + Add team button in the sidebar. When creating new teams, you'll have the option to copy over settings from an existing team.
To access team settings, hover over the team name in the lefthand sidebar, click the
··· and then Team settings. Open workspace settings, then scroll down to the bottom of the lefthand sidebar.
If you aren't sure how to split up your teams, default to starting with fewer teams. It's easy to add more teams in the future and move issues from one team to another.
Many settings in Linear are team-specific. On the plus side, that means these settings can be configured differently to support different ways that teams work. On the negative side, it means that some settings you might prefer be changed globally must be updated for every team (unless you use the copy team settings options during team creation).
Here are some things to keep in mind when deciding how to split up teams:
- Issues are tied to teams. Think about how you prefer to manage your work and interact with features such as the backlog and archive.
- Workflows can be customized per team. Different work areas or internal teams (e.g. engineering, design, marketing, sales) may require different statuses.
- Cycles are team-specific. You can set them up so that all teams follow the same schedule, but you can't view more than one team's cycle at once. Think about how you manage your work, run meetings, measure progress, and how many cycles you'll want to oversee as a manager.
- Projects can be shared across multiple teams. You can view a roadmap for your organization or team roadmaps.
- Sub-issues can be assigned to any team or member in the workspace, not just the parent issue's team.
- Other features are team-specific but also easy to copy over to another team, such as pull request automation and issue templates. Labels are team-specific but you can create views that show issues from multiple teams as long as the label has the same name across them.
All members of a workspace can view and join teams as long as the team is not private. Anyone in the workspace can create issues for other teams or be assigned issues in other teams, too. You don't have to join teams to collaborate with others unless you use them frequently and want them to show up in your sidebar.
Admins can add users to teams under Members in team settings. Members can join and leave teams on their own, by hovering over the team name in the lefthand sidebar, then clicking the
··· and selecting to join or leave the team. To join a private team, members must be invited by the team owner.
We list your teams first, then other teams in the left-hand sidebar. If you don't see other teams showing up, click on Other teams to unfurl the list, then on the specific team to view its default pages and views.
In the Team settings page, you can change the icon beside a team name to any of the Linear icons or an emoji of your choice.
You can customize the team name and identifier from here also.
Here's a quick summary of where to find settings for various features in Linear:
Workflows and statuses
Cycles and their duration
Auto-close and Auto-archive
Git automation (how status changes with PR/MR changes)
Priority ordering on views
Team Slack notifications
Use Cmd/Ctrl Shift M to move an issue to a new team or take the action from the three dot (more) menu in the full issue view or contextual menu. You'll lose team-specific data such as cycles, labels, projects, and statuses when you move issues but there are existing workarounds.
To move issues in bulk, filter the issues, use Cmd A to select all of them, and then take the action to move issues to a new team. It is not possible to move issues across Linear workspaces but you can use the CLI importer to import those issues.