Linear

Linear's AI features center on triage and drafting assistance -- suggesting labels, priority, or a likely assignee for an incoming issue, and helping draft or clean up issue descriptions -- rather than an autonomous agent that resolves or closes issues on its own. Availability of specific AI features has expanded over time and can vary by plan.

Practical Details

AI-suggested triage decisions (priority, labels, assignee) are recommendations for a human to confirm in the Triage view, not automatic actions applied without review. This is distinct from Linear's rule-based automations (like auto-closing an issue on PR merge), which are deterministic and don't involve AI judgment.

Actionable Considerations

1. Review AI-suggested triage decisions (priority, labels, assignee) before confirming them, rather than treating them as final.
2. Confirm which AI features are included on your specific plan, since availability has expanded incrementally.
3. Don't confuse AI-assisted triage suggestions with Linear's separate rule-based automations like merge-triggered issue closing.

Linear's plans are Free, Basic, Business, and Enterprise, priced per seat on paid tiers -- the Free plan caps active issues at 250 and limits file storage, which is the practical trigger for most small teams to upgrade rather than a feature gate. SAML SSO, SCIM provisioning, and the audit log are Enterprise-only features, not available by paying for more seats on Business.

Practical Details

Guest seats (for external collaborators with scoped access) are billed differently from full member seats on plans that support them, so it's worth checking current guest-seat terms rather than assuming they're free or unlimited. Linear bills per active member seat, so removing inactive members directly reduces cost rather than requiring a plan downgrade.

Actionable Considerations

• Check the Free plan's 250 active-issue cap and file storage limit before assuming it covers a growing team.
• Confirm SAML SSO, SCIM, and the audit log require the Enterprise plan specifically, not just more Business seats.
• Remove inactive member seats promptly, since Linear bills per active seat rather than a flat organizational fee.

Linear scales through its Team structure -- each Team has its own issue numbering, workflow states, and backlog, so a growing organization typically adds Teams rather than cramming every department into one shared backlog. Cross-team work is coordinated through Projects and Initiatives that can span multiple Teams rather than duplicating issues.

Practical Details

Cycles (Linear's time-boxed iteration feature) automatically roll over incomplete issues to the next cycle, which keeps a growing backlog from silently accumulating stale, unscoped work if cycles are actually being used and reviewed. Linear's free tier caps active issues at 250, which is a real constraint to check before scaling usage on a free workspace.

Actionable Considerations

1. Add new Teams as the organization grows rather than expanding one Team's backlog indefinitely.
2. Use Cycles' automatic rollover as a forcing function to review stale issues, rather than letting a backlog grow unbounded.
3. Check the free tier's 250 active-issue cap before scaling usage, since exceeding it requires a paid plan.

A practical Linear rollout starts with one team's real workflow states (not Linear's generic defaults left unmodified) and a small set of issue templates that match how that team actually files bugs and feature requests, rather than trying to standardize the whole organization on day one.

Practical Details

Linear's own published "Linear Method" -- a set of opinionated practices around Cycles, small well-scoped issues, and weekly planning -- is a useful reference for teams new to the tool, though not every team needs to adopt it wholesale. Initiatives (a layer above Projects) are worth introducing once you have multiple projects that need grouping under a shared goal, not from day one.

Actionable Considerations

1. Customize workflow states and issue templates to one team's real process before rolling Linear out more broadly.
2. Reference Linear's published "Linear Method" for practices around Cycles and issue scoping, without assuming your team must adopt every part of it.
3. Introduce Initiatives only once you have multiple related Projects that genuinely need grouping under a shared goal.

Teams adopting Linear generally notice the difference most in issue-writing discipline and cycle-based planning rather than a passive productivity boost -- Linear's opinionated structure (Cycles, Triage, small well-scoped issues) tends to surface whether a team's existing process was actually being followed, not just add a new tool on top of an unclear one.

Practical Details

Linear's Insights feature (plan-dependent) provides basic velocity and cycle-completion reporting, which is a more honest engagement signal than subjective impressions of whether the team feels more organized. Adoption tends to stall when teams import a messy backlog wholesale rather than starting with a smaller, actively-maintained set of issues.

Actionable Considerations

• Use Cycles and Triage as intended -- as a forcing function for scoping and reviewing work -- rather than treating them as optional.
• Check Insights (plan-dependent) for velocity and completion data rather than relying on a subjective sense of team organization.
• Start with a smaller, actively-curated backlog rather than importing years of stale issues wholesale during initial adoption.

Linear is organized around Teams (each with its own backlog and issue-numbering prefix, like ENG or DES), Projects (a grouping of related issues with a target date), and Cycles (time-boxed iterations similar to sprints). Setup means creating your first Team, then deciding whether to import existing issues from a tool like Jira or start fresh.

Setup Considerations

Linear's importers support Jira, GitHub Issues, Asana, and a few other tools, mapping existing statuses and assignees where possible -- worth reviewing the mapping before a full import rather than assuming it's a perfect match. Linear is built around keyboard shortcuts and the command palette (Cmd/Ctrl+K) as the primary navigation method, which is a real adjustment for teams coming from a mouse-driven tool.

Actionable Considerations

1. Create your first Team with a short issue prefix (like ENG) before inviting the broader organization.
2. Review the import mapping carefully if migrating from Jira or another tool, rather than assuming statuses and assignees transfer perfectly.
3. Introduce the command palette (Cmd/Ctrl+K) early, since Linear's workflow is designed around keyboard navigation rather than mouse-driven menus.
4. Decide on Team structure (by function vs. by product area) before inviting the whole organization, since restructuring later means moving issues across Teams.

Linear's access model is scoped by Team membership and workspace-level roles (Admin, Member, Guest) -- a Guest can be given access to specific issues or projects without full workspace visibility, which is the mechanism for bringing in external collaborators without over-provisioning access. SAML SSO and SCIM provisioning are available on Linear's Enterprise plan, not lower tiers.

Practical Details

Linear's audit log (Enterprise plan) tracks workspace-level security events like member and permission changes, which is separate from an issue's own activity history that any plan can see. Two-factor authentication is available account-wide regardless of plan tier.

Actionable Considerations

• Use Guest access to scope external collaborators to specific issues or projects rather than granting full workspace membership.
• Confirm SAML SSO and SCIM provisioning are only available on the Enterprise plan before assuming lower tiers include them.
• Enable two-factor authentication for all members regardless of plan, since it's not gated behind Enterprise.

Linear's primary support channels are its documentation site and an in-app feedback/support widget, with response times and dedicated support access varying by plan tier -- Enterprise customers get more direct support access than teams on lower tiers. Linear doesn't run a large paid professional-services or certification program the way some enterprise tools do; most onboarding happens through self-serve docs and the product's own guided setup.

Practical Details

Linear's public roadmap and changelog are worth following directly, since the product ships frequent incremental updates and features referenced in older third-party guides can shift. The community also maintains unofficial resources (templates, workflow guides) worth checking alongside official docs.

Actionable Considerations

• Check Linear's own changelog and public roadmap for current feature details, since the product updates frequently.
• Use the in-app support widget for direct questions rather than assuming a dedicated account manager on lower plan tiers.
• Review both official docs and community-maintained resources when setting up templates or workflows, since practices evolve.

Linear's tightest integration is with Git -- connecting a GitHub or GitLab repo lets you create a branch directly from an issue (auto-named with the issue identifier, like username/eng-123-fix-thing), and a linked pull request can automatically move the issue through your workflow states and close it on merge. Linear also has a Slack integration for creating issues from messages and posting status updates back to a channel.

Practical Details

Triage is Linear's dedicated intake view -- issues created via Slack, email, the API, or an integration like Intercom land in Triage first rather than going straight into a team's backlog, so someone has to actively accept or route them. Linear's GraphQL API and webhooks cover custom automation beyond the built-in integrations.

Actionable Considerations

• Connect your Git provider to get automatic branch naming and merge-triggered issue transitions, rather than updating issue status manually after every PR.
• Use Triage as the review gate for issues coming from Slack, email, or other integrations before they enter a team's active backlog.
• Reach for the GraphQL API or webhooks for custom automation beyond what the built-in Slack/Git integrations cover.