Table: linear_team - Query Linear Teams using SQL

Linear is a software development management tool that allows teams to streamline their workflow. It provides a centralized platform for managing tasks, tracking progress, and coordinating team efforts. With Linear, teams can effectively collaborate, manage their tasks, and track their progress to ensure efficient project completion.

Table Usage Guide

The linear_team table provides insights into team structures within Linear. As a project manager or team lead, explore team-specific details through this table, including team members, associated tasks, and progress status. Utilize it to uncover information about teams, such as their workflows, the distribution of tasks, and the overall progress of the team in the project.

Examples

Basic info

Explore the characteristics of your team settings on Linear, such as creation date, privacy settings, and triage capabilities. This can help you understand the current configuration and make necessary adjustments for better project management.

select
  id,
  title,
  created_at,
  color,
  private,
  triage_enabled,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team;

select
  id,
  title,
  created_at,
  color,
  private,
  triage_enabled,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team;

List public teams

Explore the various public teams within your organization, allowing you to assess their characteristics and settings. This can help in understanding team structures and their respective configurations, which can be beneficial in managing resources and planning workflows.

select
  id,
  title,
  created_at,
  color,
  private,
  triage_enabled,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team
where
  not private;

select
  id,
  title,
  created_at,
  color,
  private,
  triage_enabled,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team
where
  not private;

List teams that are not using cycles

Discover the teams that have opted not to use cycles, providing insights into their work methodology and allowing for potential process optimization. This can be useful for assessing the effectiveness of various team strategies.

select
  id,
  title,
  created_at,
  color,
  private,
  triage_enabled,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team
where
  not cycles_enabled;

select
  id,
  title,
  created_at,
  color,
  private,
  triage_enabled,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team
where
  not cycles_enabled;

List teams that are not associated with any integration

Discover the teams that lack any associated integrations, enabling you to assess areas for potential improvement in team collaboration and productivity.

select
  id,
  title,
  created_at,
  color,
  private,
  triage_enabled,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team
where
  integrations_settings is null;

select
  id,
  title,
  created_at,
  color,
  private,
  triage_enabled,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team
where
  integrations_settings is null;

List archived teams

Explore which teams have been archived in your Linear organization. This can help you keep track of past teams and their settings, providing valuable context for organizational planning and resource allocation.

select
  id,
  title,
  created_at,
  color,
  private,
  triage_enabled,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team
where
  archived_at is not null;

select
  id,
  title,
  created_at,
  color,
  private,
  triage_enabled,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team
where
  archived_at is not null;

List teams where triage mode is enabled

Discover the segments that have the triage mode activated, allowing you to understand which teams are set up for crisis management. This is particularly beneficial in assessing the readiness of different teams in handling urgent issues.

select
  id,
  title,
  created_at,
  color,
  private,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team
where
  triage_enabled;

select
  id,
  title,
  created_at,
  color,
  private,
  key,
  default_issue_estimate,
  auto_close_period,
  updated_at
from
  linear_team
where
  triage_enabled = 1;

Schema for linear_team

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
active_cycle	jsonb		Team's currently active cycle.
archived_at	timestamp with time zone		The time at which the team was archived (if it has been).
auto_archive_period	bigint		The period (in months) after which automatically closed and completed issues are automatically archived.
auto_close_period	bigint		The period (in months) after which issues are automatically closed. Null/undefined means this feature is disabled.
auto_close_state_id	text		The canceled workflow state which auto closed issues will be set to. Defaults to the first canceled state.
color	text		The team's color.
created_at	timestamp with time zone	=, >, >=, <=, <	The time at which the team was created.
cycle_calender_url	text		Calendar feed URL (iCal) for cycles.
cycle_cooldown_time	bigint		The cooldown time after each cycle in weeks.
cycle_duration	bigint		The duration of a cycle in weeks.
cycle_issue_auto_assign_completed	boolean		Whether completed issues are automatically assigned to the current cycle.
cycle_issue_auto_assign_started	boolean		Whether started issues are automatically assigned to the current cycle.
cycle_lock_to_active	boolean		Whether only issues with cycles in Active Issues are allowed.
cycle_start_day	text		The day of the week that a new cycle starts.
cycles_enabled	boolean		Whether the team uses cycles.
default_issue_estimate	bigint		The default estimate for unestimated issues.
default_issue_state	jsonb		The default workflow state into which issues are set when they are opened by team members.
default_template_for_members	jsonb		The default template to use for new issues created by members of the team.
default_template_for_members_id	text		The ID of the default template to use for new issues created by members of the team.
default_template_for_non_members	jsonb		The default template to use for new issues created by non-members of the team.
default_template_for_non_members_id	text		The ID of the default template to use for new issues created by non-members of the team.
description	text		The team's description.
draft_workflow_state	jsonb		The workflow state into which issues are moved when a PR has been opened as draft.
group_issue_history	boolean		Whether to group recent issue history entries.
icon	text		The team's icon.
id	text	=	A unique identifier for the team.
integrations_settings	jsonb		Settings for all integrations associated with that team.
invite_hash	text		A unique hash for the team to be used in invite URLs.
issue_estimation_allow_zero	boolean		Whether to allow zeros in issues estimates.
issue_estimation_extended	boolean		Whether to add additional points to the estimate scale.
issue_estimation_type	text		The issue estimation type to use.
issue_ordering_no_priority_first	boolean		Whether issues without priority should be sorted first.
issue_sort_order_default_to_bottom	boolean		Whether to move issues to bottom of the column when changing state.
key	text	=	The team's unique key. The key is used in URLs.
marked_as_duplicate_workflow_state	jsonb		The workflow state into which issues are moved when they are marked as a duplicate of another issue. Defaults to the first canceled state.
name	text	=	The team's name.
organization	jsonb		The organization that the team is associated with.
organization_id	text	=, !=, ~~, ~~, !~~, !~~	Unique identifier for the organization.
private	boolean		Whether the team is private or not.
require_priority_to_leave_triage	boolean		Whether an issue needs to have a priority set before leaving triage.
review_workflow_state	jsonb		The workflow state into which issues are moved when a review has been requested for the PR.
slack_issue_comments	boolean		Whether to send new issue comment notifications to Slack.
slack_issue_statuses	boolean		Whether to send new issue status updates to Slack.
slack_new_issue	boolean		Whether to send new issue notifications to Slack.
sp_connection_name	text	=, !=, ~~, ~~, !~~, !~~	Steampipe connection name.
sp_ctx	jsonb		Steampipe context in JSON form.
start_workflow_state	jsonb		The workflow state into which issues are moved when a PR has been opened.
timezone	text		The timezone of the team. Defaults to 'America/Los_Angeles'
title	text		The team's title.
triage_enabled	boolean		Whether triage mode is enabled for the team or not.
triage_issue_state	jsonb		The workflow state into which issues are set when they are opened by non-team members or integrations if triage is enabled.
upcoming_cycle_count	double precision		How many upcoming cycles to create.
updated_at	timestamp with time zone	=, >, >=, <=, <	The last time at which the entity was meaningfully updated, i.e. for all changes of syncable properties except those for which updates should not produce an update to updatedAt (see skipUpdatedAtKeys). This is the same as the creation time if the entity hasn't been updated after creation.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- linear

You can pass the configuration to the command with the --config argument:

steampipe_export_linear --config '<your_config>' linear_team