steampipe plugin install linear

Table: linear_issue - Query Linear Issues using SQL

Linear is a project management and issue tracking tool. It helps teams plan, track, and coordinate tasks across their projects. It provides a streamlined way to manage software projects, tasks, and bug tracking, ensuring teams stay on track and meet their goals.

Table Usage Guide

The linear_issue table provides insights into issues within Linear's project management tool. As a project manager or team lead, explore issue-specific details through this table, including statuses, assignees, and associated metadata. Utilize it to uncover information about issues, such as their current progress, the team members assigned to them, and their priority levels.

Examples

Basic info

Explore the issues in your project, including their creation date, branch name, priority, and estimate time, to manage your workflow and prioritize tasks more effectively. This query helps you gain insights into the status of different issues, allowing you to make informed decisions and streamline your project management process.

select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue;
select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue;

List urgent issues

Discover the segments that contain high-priority tasks in your workflow. This query assists in identifying urgent issues that require immediate attention, helping to prioritize and manage tasks effectively.

select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
priority = 1;
select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
priority = 1;

List issues that have not been started

Identify instances where certain issues have yet to begin, allowing for better prioritization and task management.

select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
started_at is null;
select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
started_at is null;

List issues that have crossed the due date

Discover the segments that have missed their deadlines by identifying issues that have surpassed their due dates. This can be useful in project management to assess the elements within your workflow that need attention or re-evaluation.

select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
due_date < now();
select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
due_date < datetime('now');

List trashed issues

Explore which issues have been moved to trash on Linear. This can assist in tracking the progress of tasks and identifying any potential bottlenecks or problems that have led to tasks being discarded.

select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
trashed;
select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
trashed = 1;

List issues created by admin

Identify instances where administrative users have created issues. This allows for a quick overview of issues which may have higher priority or require more immediate attention.

select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
creator ->> 'admin' = 'true';
select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
json_extract(creator, '$.admin') = 'true';

List issues of a particular team

Explore which issues are currently being handled by a specific team. This can help in understanding the team's workload, priority tasks, and the timeline of their projects.

select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
team ->> 'name' = 'linear';
select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
json_extract(team, '$.name') = 'linear';

List unassigned issues

Explore which issues are currently unassigned, allowing you to understand bottlenecks and allocate resources more effectively. This is particularly useful for project management and ensuring tasks are not overlooked.

select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
assignee is null;
select
id,
title,
created_at,
branch_name,
priority,
estimate,
updated_at
from
linear_issue
where
assignee is null;

Schema for linear_issue

NameTypeOperatorsDescription
_ctxjsonbSteampipe context in JSON form, e.g. connection_name.
archived_attimestamp with time zoneThe time at which the entity was archived. Null if the entity has not been archived.
assigneejsonbThe user to whom the issue is assigned to.
auto_archived_attimestamp with time zone=, >, >=, <=, <The time at which the issue was automatically archived by the auto pruning process.
auto_closed_attimestamp with time zone=, >, >=, <=, <The time at which the issue was automatically closed by the auto pruning process.
branch_nametextSuggested branch name for the issue.
canceled_attimestamp with time zone=, >, >=, <=, <The time at which the issue was moved into canceled state.
completed_attimestamp with time zone=, >, >=, <=, <The time at which the issue was moved into completed state.
created_attimestamp with time zone=, >, >=, <=, <The time at which the entity was created.
creatorjsonbThe user who created the issue.
customer_ticket_countbigintReturns the number of Attachment resources which are created by customer support ticketing systems (e.g. Zendesk).
cyclejsonbThe cycle that the issue is associated with.
descriptiontextThe issue's description in markdown format.
due_datetimestamp with time zone=, >, >=, <=, <The date at which the issue is due.
estimatedouble precisionThe estimate of the complexity of the issue.
idtext=The unique identifier of the entity.
identifiertextIssue's human readable identifier (e.g. ENG-123).
numberdouble precision=, >, >=, <=, <The issue's unique number.
parentjsonbThe parent of the issue.
previous_identifiersjsonbPrevious identifiers of the issue if it has been moved between teams.
prioritydouble precision=, >, >=, <=, <The priority of the issue. 0 = No priority, 1 = Urgent, 2 = High, 3 = Normal, 4 = Low.
priority_labeltextLabel for the priority.
projectjsonbThe project that the issue is associated with.
project_milestonejsonbThe projectMilestone that the issue is associated with.
snoozed_byjsonbThe user who snoozed the issue.
snoozed_until_attimestamp with time zone=, >, >=, <=, <The time until an issue will be snoozed in Triage view.
sort_orderdouble precisionThe order of the item in relation to other items in the organization.
started_attimestamp with time zone=, >, >=, <=, <The time at which the issue was moved into started state.
statejsonbThe workflow state that the issue is associated with.
sub_issue_sort_orderdouble precisionThe order of the item in the sub-issue list. Only set if the issue has a parent.
teamjsonbThe team that the issue is associated with.
titletext=The issue's title.
trashedbooleanA flag that indicates whether the issue is in the trash bin.
updated_attimestamp with time zone=, >, >=, <=, <The last time at which the entity was meaningfully updated. This is the same as the creation time if the entity hasn't been updated after creation.
urltextIssue 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_issue