Table: linear_organization - Query Linear Organizations using SQL
Linear is a project management tool that streamlines software projects, tasks, and bug tracking. It's designed for high-performance teams to drive their work forward. With Linear, teams can plan, organize, and track all their software development processes in one place.
Table Usage Guide
The linear_organization
table provides insights into organizations within Linear. As a project manager or team lead, you can use this table to get detailed information about your organization, including its name, domain, and associated attributes. This can be particularly useful for managing and organizing your software development processes more efficiently.
Examples
Basic info
Explore which organizations have enabled the roadmap feature and assess the user count for each to gain insights into their release channels. This can help in understanding the usage trends and making informed decisions.
select id, title, created_at, url_key, user_count, roadmap_enabled, release_channel, updated_atfrom linear_organization;
select id, title, created_at, url_key, user_count, roadmap_enabled, release_channel, updated_atfrom linear_organization;
List teams in the organization
Explore the different teams within your organization to understand their characteristics and recent updates. This can assist in managing team-specific resources or assessing the overall structure of your organization.
select t.id, t.title, t.color, t.key, t.private, t.updated_atfrom linear_team as t, linear_organization as owhere o.id = t.organization ->> 'id';
select t.id, t.title, t.color, t.key, t.private, t.updated_atfrom linear_team as t, linear_organization as owhere o.id = json_extract(t.organization, '$.id');
List users in the organization
Explore which users are active within your organization and gain insights into their administrative status and last update time. This can be particularly useful for managing user roles and tracking activity.
select u.id, u.title, u.active, u.admin, u.email, u.updated_atfrom linear_user as u, linear_organization as owhere o.id = u.organization ->> 'id';
select u.id, u.title, u.active, u.admin, u.email, u.updated_atfrom linear_user as u, linear_organization as owhere o.id = json_extract(u.organization, '$.id');
List integrations in the organization
Explore which integrations are present within the organization. This can be used to identify the tools and services being utilized, aiding in resource management and strategic planning.
select i.id, i.created_at, i.service, i.updated_atfrom linear_integration as i, linear_organization as owhere o.id = i.organization ->> 'id';
select i.id, i.created_at, i.service, i.updated_atfrom linear_integration as i, linear_organization as owhere o.id = json_extract(i.organization, '$.id');
Show subscription details of the organization
Determine the specifics of your organization's subscription, including the number of seats and type of subscription, and gain insights into future billing dates and creation times. This can help in managing your organization's resources and planning for future expenses.
select subscription ->> 'id' as creator_id, subscription ->> 'nextBillingAt' as next_billing_at, subscription ->> 'seats' as seats, subscription ->> 'type' as type, subscription ->> 'createdAt' as created_atfrom linear_organization;
select json_extract(subscription, '$.id') as creator_id, json_extract(subscription, '$.nextBillingAt') as next_billing_at, json_extract(subscription, '$.seats') as seats, json_extract(subscription, '$.type') as type, json_extract(subscription, '$.createdAt') as created_atfrom linear_organization;
List organizations that have roadmap enabled
Discover the segments that have the roadmap feature enabled, which allows you to manage your organization's future plans and developments more effectively.
select id, title, created_at, url_key, user_count, roadmap_enabled, release_channel, updated_atfrom linear_organizationwhere roadmap_enabled;
select id, title, created_at, url_key, user_count, roadmap_enabled, release_channel, updated_atfrom linear_organizationwhere roadmap_enabled = 1;
List the organizations with SAML authentication enabled
Discover the organizations that have enabled SAML authentication to understand their security measures and manage user access more efficiently.
select id, title, created_at, url_key, user_count, saml_enabled, release_channel, updated_atfrom linear_organizationwhere saml_enabled;
select id, title, created_at, url_key, user_count, saml_enabled, release_channel, updated_atfrom linear_organizationwhere saml_enabled = 1;
List the organizations with SCIM provisioning enabled
Discover the segments that have SCIM provisioning enabled in their organizations. This can be useful in assessing the level of security and user management within these organizations.
select id, title, created_at, url_key, user_count, scim_enabled, release_channel, updated_atfrom linear_organizationwhere scim_enabled;
select id, title, created_at, url_key, user_count, scim_enabled, release_channel, updated_atfrom linear_organizationwhere scim_enabled = 1;
Schema for linear_organization
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
allowed_auth_services | jsonb | Allowed authentication providers, empty array means all are allowed | |
archived_at | timestamp with time zone | The time at which the entity was archived. Null if the entity has not been archived. | |
created_at | timestamp with time zone | The time at which the entity was created. | |
created_issue_count | bigint | Number of issues in the organization. | |
deletion_requested_at | timestamp with time zone | The time at which deletion of the organization was requested. | |
git_branch_format | text | How git branches are formatted. If null, default formatting will be used. | |
git_linkback_messages_enabled | boolean | Whether the Git integration linkback messages should be sent to private repositories. | |
git_public_linkback_messages_enabled | boolean | Whether the Git integration linkback messages should be sent to public repositories. | |
id | text | The unique identifier of the entity. | |
logo_url | text | The organization's logo URL. | |
name | text | The organization's name. | |
organization_id | text | =, !=, ~~, ~~*, !~~, !~~* | Unique identifier for the organization. |
period_upload_volume | double precision | Rolling 30-day total upload volume for the organization, in megabytes. | |
previous_url_keys | jsonb | Previously used URL keys for the organization (last 3 are kept and redirected). | |
project_update_reminders_day | text | The day at which to prompt for project updates. | |
project_update_reminders_hour | double precision | The hour at which to prompt for project updates. | |
project_updates_reminder_frequency | text | The frequency at which to prompt for project updates. | |
release_channel | text | The feature release channel the organization belongs to. | |
roadmap_enabled | boolean | Whether the organization is using a roadmap. | |
saml_enabled | boolean | Whether SAML authentication is enabled for organization. | |
scim_enabled | boolean | Whether SCIM provisioning is enabled for organization. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
subscription | jsonb | The organization's subscription to a paid plan. | |
title | text | The organization's title. | |
trial_ends_at | timestamp with time zone | The time at which the trial of the plus plan will end. | |
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. | |
url_key | text | The organization's unique URL key. | |
user_count | bigint | Number of active users in the organization. |
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_organization