Table: linear_comment - Query Linear Comments using SQL

Linear Comment is a feature within Linear that allows users to communicate and collaborate on issues, projects, and cycles. It provides a centralized way to manage and view comments made by team members, enhancing transparency and facilitating discussions. Linear Comment helps you stay informed about the progress and updates of your Linear resources and understand the context of decisions and changes.

Table Usage Guide

The linear_comment table provides insights into comments within Linear. As a project manager or team lead, explore comment-specific details through this table, including the author, text, created and updated timestamps, and associated issue. Utilize it to uncover information about comments, such as those related to specific issues, the frequency of updates, and the involvement of team members in discussions.

Examples

Basic info

Explore the timeline of user interactions with your platform by identifying when specific comments were created, edited, or updated. This allows for a better understanding of user engagement patterns over time.

select
  id,
  title,
  created_at,
  edited_at,
  updated_at,
  url
from
  linear_comment;

select
  id,
  title,
  created_at,
  edited_at,
  updated_at,
  url
from
  linear_comment;

Show user details of each comment

Explore the details of users who have made comments, including their active status and administrative privileges. This can be useful for understanding user engagement and identifying key contributors.

select
  id,
  title,
  comment_user ->> 'id' as creator_id,
  comment_user ->> 'name' as creator_name,
  comment_user ->> 'active' as active,
  comment_user ->> 'email' as email,
  comment_user ->> 'admin' as admin,
  comment_user ->> 'createdAt' as created_at
from
  linear_comment;

select
  id,
  title,
  json_extract(comment_user, '$.id') as creator_id,
  json_extract(comment_user, '$.name') as creator_name,
  json_extract(comment_user, '$.active') as active,
  json_extract(comment_user, '$.email') as email,
  json_extract(comment_user, '$.admin') as admin,
  json_extract(comment_user, '$.createdAt') as created_at
from
  linear_comment;

List comments for a particular issue

Explore the comments related to a specific issue to gain insights into its history and ongoing discussions. This can be useful for understanding the context and progression of the issue, as well as for tracking any changes or edits made over time.

select
  id,
  title,
  created_at,
  edited_at,
  updated_at,
  url
from
  linear_comment
where
  issue ->> 'title' = 'attachment check';

select
  id,
  title,
  created_at,
  edited_at,
  updated_at,
  url
from
  linear_comment
where
  json_extract(issue, '$.title') = 'attachment check';

List comments written by admin

Explore which comments have been authored by an admin user. This can help in understanding the context and engagement of administrative users in discussions.

select
  id,
  title,
  created_at,
  edited_at,
  comment_user,
  url
from
  linear_comment
where
  comment_user ->> 'admin' = 'true';

select
  id,
  title,
  created_at,
  edited_at,
  comment_user,
  url
from
  linear_comment
where
  json_extract(comment_user, '$.admin') = 'true';

List comments older than 90 days

Discover the segments that contain comments older than 90 days to better understand user feedback trends and manage content accordingly. This is useful for identifying outdated or irrelevant discussions and maintaining a current and engaging user experience.

select
  id,
  title,
  created_at,
  edited_at,
  updated_at,
  url
from
  linear_comment
where
  created_at < now() - interval '90' day;

select
  id,
  title,
  created_at,
  edited_at,
  updated_at,
  url
from
  linear_comment
where
  created_at < datetime('now', '-90 day');

Schema for linear_comment

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.
body	text	=	The comment content in markdown format.
body_data	text		The comment content as a Prosemirror document.
comment_user	jsonb		The user who wrote the comment.
created_at	timestamp with time zone	=, >, >=, <=, <	The time at which the entity was created.
edited_at	timestamp with time zone		The time user edited the comment.
id	text	=	The unique identifier of the entity.
issue	jsonb		The issue that the comment is associated with.
organization_id	text	=, !=, ~~, ~~, !~~, !~~	Unique identifier for the organization.
parent	jsonb		The parent comment under which the current comment is nested.
reaction_data	jsonb		Emoji reaction summary, grouped by emoji type.
sp_connection_name	text	=, !=, ~~, ~~, !~~, !~~	Steampipe connection name.
sp_ctx	jsonb		Steampipe context in JSON form.
title	text		The comment'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		Comment's 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_comment