Table: linear_project - Query Linear Projects using SQL
Linear Project is a resource in Linear, a software development management tool. It allows users to organize tasks, issues, and objectives into specific projects. Each project in Linear has a unique identifier, name, and status, and may contain additional details such as description, label, and team information.
Table Usage Guide
The linear_project
table provides insights into projects within Linear. As a project manager or a software development team member, you can explore project-specific details through this table, including their status, description, and associated team information. Utilize it to manage and monitor the progress of different projects, understand their scope, and ensure timely completion of tasks and objectives.
Examples
Basic info
Discover the segments that are currently in progress within your projects and assess their status and timeline. This can help you understand the overall progress and manage your projects more efficiently.
select id, title, created_at, color, progress, scope, state, updated_atfrom linear_project;
select id, title, created_at, color, progress, scope, state, updated_atfrom linear_project;
List planned projects
Explore which projects are in the planning stage to effectively manage resources and prioritize tasks. This aids in strategic decision-making by providing insights into upcoming projects.
select id, title, created_at, color, progress, scope, state, updated_atfrom linear_projectwhere state = 'planned';
select id, title, created_at, color, progress, scope, state, updated_atfrom linear_projectwhere state = 'planned';
List projects which are incomplete
Explore which projects are still ongoing. This is useful for tracking progress and identifying tasks that may need additional resources or attention.
select id, title, created_at, color, progress, scope, state, updated_atfrom linear_projectwhere completed_at is null;
select id, title, created_at, color, progress, scope, state, updated_atfrom linear_projectwhere completed_at is null;
List projects created by admin
Discover the projects that were established by administrative users. This can be particularly useful for auditing or understanding the distribution of project creation responsibilities within your team.
select id, title, created_at, color, progress, scope, state, updated_atfrom linear_projectwhere creator ->> 'admin' = 'true';
select id, title, created_at, color, progress, scope, state, updated_atfrom linear_projectwhere json_extract(creator, '$.admin') = 'true';
Show lead details of each project
Explore the leadership details of each project to gain insights into their activity status and roles. This can help in assessing the active involvement and administrative roles of the leads in different projects.
select lead ->> 'id' as lead_id, lead ->> 'name' as name, lead ->> 'email' as email, lead ->> 'active' as active, lead ->> 'admin' as admin, lead ->> 'statusLabel' as status_labelfrom linear_project;
select json_extract(lead, '$.id') as lead_id, json_extract(lead, '$.name') as name, json_extract(lead, '$.email') as email, json_extract(lead, '$.active') as active, json_extract(lead, '$.admin') as admin, json_extract(lead, '$.statusLabel') as status_labelfrom linear_project;
Schema for linear_project
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
archived_at | timestamp with time zone | The time at which the entity was archived. Null if the entity has not been archived. | |
auto_archived_at | timestamp with time zone | The time at which the project was automatically archived by the auto pruning process. | |
canceled_at | timestamp with time zone | The time at which the project was moved into canceled state. | |
color | text | The project's color. | |
completed_at | timestamp with time zone | The time at which the project was moved into completed state. | |
completed_issue_count_history | jsonb | The number of completed issues in the project after each week. | |
completed_scope_history | jsonb | The number of completed estimation points after each week. | |
converted_from_issue | jsonb | The project was created based on this issue. | |
created_at | timestamp with time zone | =, >, >=, <=, < | The time at which the entity was created. |
creator | jsonb | The user who created the project. | |
description | text | The project's description. | |
icon | text | The icon of the project. | |
id | text | = | The unique identifier of the entity. |
in_progress_scope_history | jsonb | The number of in progress estimation points after each week. | |
integrations_settings | jsonb | Settings for all integrations associated with that project. | |
issue_count_history | jsonb | The total number of issues in the project after each week. | |
lead | jsonb | The project lead. | |
name | text | = | The project's name. |
organization_id | text | =, !=, ~~, ~~*, !~~, !~~* | Unique identifier for the organization. |
progress | double precision | The overall progress of the project. This is the (completed estimate points + 0.25 * in progress estimate points) / total estimate points. | |
project_update_reminders_paused_until_at | timestamp with time zone | The time until which project update reminders are paused. | |
scope | double precision | The overall scope (total estimate points) of the project. | |
scope_history | jsonb | The total number of estimation points after each week. | |
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. | |
slug_id | text | = | The project's unique URL slug. |
sort_order | double precision | The sort order for the project within the organization. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
start_date | timestamp with time zone | =, >, >=, <=, < | The estimated start date of the project. |
started_at | timestamp with time zone | The time at which the project was moved into started state. | |
state | text | = | The type of the state. |
target_date | timestamp with time zone | =, >, >=, <=, < | The estimated completion date of the project. |
title | text | The project's title. | |
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 | text | Project URL. |
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_project