Expand description
GraphQL object types.
Generated by lineark-codegen — do not edit.
Structs§
- Actor
Bot - A bot actor representing a non-human entity that performed an action, such as an integration (GitHub, Slack, Zendesk), an AI assistant, or an automated workflow. Bot actors are displayed in activity feeds and history to indicate when changes were made by applications rather than users.
- Agent
Activity - An activity performed by or directed at an AI coding agent during a session. Activities represent the observable steps of an agent’s work, including thoughts, actions (tool calls), responses, prompts from users, errors, and elicitation requests. Each activity belongs to an agent session and is associated with the user who initiated it.
- Agent
Activity Action Content - Content for an action activity (tool call or action).
- Agent
Activity Connection - Agent
Activity Edge - Agent
Activity Elicitation Content - Content for an elicitation activity.
- Agent
Activity Error Content - Content for an error activity.
- Agent
Activity Payload - The result of an agent activity mutation.
- Agent
Activity Prompt Content - Content for a prompt activity.
- Agent
Activity Response Content - Content for a response activity.
- Agent
Activity Thought Content - Content for a thought activity.
- Agent
Session - A session representing an AI coding agent’s work on an issue or conversation. Agent sessions track the lifecycle of an agent’s engagement, from creation through active work to completion or dismissal. Each session is associated with an agent user (the bot), optionally a human creator, an issue, and a comment thread where the agent posts updates. Sessions contain activities that record the agent’s observable steps and can be linked to pull requests created during the work.
- Agent
Session Connection - Agent
Session Edge - Agent
Session External Link - An external link associated with an agent session.
- Agent
Session Payload - Agent
Session ToPull Request - A link between an agent session and a pull request created or associated during that session. This join entity tracks which pull requests were produced by or connected to a coding agent’s work session, and handles backfilling links when pull requests are synced after the agent has already recorded the URL.
- Agent
Session ToPull Request Connection - Agent
Session ToPull Request Edge - AiConversation
InternalA conversation between a user and the Linear AI assistant. Each conversation tracks the full thread state, context references (issues, projects, documents, etc.), and conversation parts (prompts, text responses, tool calls, widgets). Conversations can originate from direct chat, issue comments, Slack threads, Microsoft Teams, or automated workflows.- AiConversation
Code Intelligence Tool Call - AiConversation
Code Intelligence Tool Call Args - AiConversation
Create Entity Tool Call - AiConversation
Create Entity Tool Call Args - AiConversation
Delete Entity Tool Call - AiConversation
Delete Entity Tool Call Args - AiConversation
Entity Card Widget - AiConversation
Entity Card Widget Args - AiConversation
Entity List Widget - AiConversation
Entity List Widget Args - AiConversation
Entity List Widget Args Entities - AiConversation
GetMicrosoft Teams Conversation History Tool Call - AiConversation
GetPull Request Diff Tool Call - AiConversation
GetPull Request Diff Tool Call Args - AiConversation
GetPull Request File Tool Call - AiConversation
GetPull Request File Tool Call Args - AiConversation
GetSlack Conversation History Tool Call - AiConversation
Handoff ToCoding Session Tool Call - AiConversation
Handoff ToCoding Session Tool Call Args - AiConversation
Invoke McpTool Tool Call - AiConversation
Invoke McpTool Tool Call Args - AiConversation
Invoke McpTool Tool Call Args Server - AiConversation
Invoke McpTool Tool Call Args Tool - AiConversation
Navigate ToPage Tool Call - AiConversation
Navigate ToPage Tool Call Args - AiConversation
Navigate ToPage Tool Call Result - AiConversation
Part Metadata - Metadata about a part in an AI conversation.
- AiConversation
Prompt Part - A prompt part in an AI conversation.
- AiConversation
Query Activity Tool Call - AiConversation
Query Activity Tool Call Args - AiConversation
Query Updates Tool Call - AiConversation
Query Updates Tool Call Args - AiConversation
Query View Tool Call - AiConversation
Query View Tool Call Args - AiConversation
Query View Tool Call Args View - AiConversation
Reasoning Part - A reasoning part in an AI conversation.
- AiConversation
Research Tool Call - AiConversation
Research Tool Call Args - AiConversation
Research Tool Call Result - AiConversation
Restore Entity Tool Call - AiConversation
Restore Entity Tool Call Args - AiConversation
Retrieve Entities Tool Call - AiConversation
Retrieve Entities Tool Call Args - AiConversation
Search Documentation Tool Call - AiConversation
Search Entities Tool Call - AiConversation
Search Entities Tool Call Args - AiConversation
Search Entities Tool Call Result - AiConversation
Search Entities Tool Call Result Entities - AiConversation
Suggest Values Tool Call - AiConversation
Suggest Values Tool Call Args - AiConversation
Text Part - A text part in an AI conversation.
- AiConversation
Tool Call Part - A tool call part in an AI conversation.
- AiConversation
Tool Display Info - AiConversation
Transcribe Media Tool Call - AiConversation
Transcribe Video Tool Call - AiConversation
Update Entity Tool Call - AiConversation
Update Entity Tool Call Args - AiConversation
WebSearch Tool Call - AiConversation
WebSearch Tool Call Args - AiConversation
Widget Display Info - AiConversation
Widget Part - A widget part in an AI conversation.
- AiPrompt
Progress InternalTracks the progress and state of an AI prompt workflow execution. Each progress record is associated with an issue or comment and contains the workflow type, current status, metadata about the execution, and optionally the conversation messages exchanged during the workflow. Progress records can form a hierarchy via parent-child relationships for multi-step workflows.- AiPrompt
Progress Connection - AiPrompt
Progress Edge - AiPrompt
Rules - Custom rules that guide AI behavior for a specific scope. Rules can be defined at the workspace level, team level, integration level, or user level, and are applied hierarchically (workspace rules first, then parent team rules, then team rules). Rules contain structured content that instructs the AI assistant on how to handle specific types of prompts, such as coding agent guidance or triage intelligence configuration.
- Application
- Public-facing information about an OAuth application. Contains only the fields that are safe to display to users during the authorization flow, excluding sensitive data like client secrets and internal configuration.
- Archive
Response - Contains requested archived model objects.
- Asks
Channel Connect Payload - Attachment
- An attachment linking external content to an issue. Attachments represent connections to external resources such as GitHub pull requests, Slack messages, Zendesk tickets, Figma files, Sentry issues, Intercom conversations, and plain URLs. Each attachment has a title and subtitle displayed in the Linear UI, a URL serving as both the link destination and unique identifier per issue, and optional metadata specific to the source integration.
- Attachment
Connection - Attachment
Edge - Attachment
Payload - The result of an attachment mutation.
- Attachment
Sources Payload - The result of an attachment sources query.
- Audit
Entry - A workspace audit log entry recording a security or compliance-relevant action. Audit entries capture who performed an action, when, from what IP address and country, and include type-specific metadata. The audit log is partitioned by time for performance and is accessible only to workspace administrators. Examples of audited actions include user authentication events, permission changes, data exports, and workspace setting modifications.
- Audit
Entry Connection - Audit
Entry Edge - Audit
Entry Type - Auth
Identity Provider - An identity provider.
- Auth
Organization - An organization. Organizations are root-level objects that contain users and teams.
- Auth
Resolver Response - Auth
User - A user that has access to the the resources of an organization.
- Authentication
Session Response - Information about an active authentication session, including the device, location, and timestamps for when it was created and last used.
- Coding
Agent Sandbox Entry InternalDetailed information about the coding agent sandbox environment associated with an agent session, including cloud infrastructure URLs for debugging and monitoring.- Coding
Agent Sandbox Payload InternalCoding agent sandbox details for an agent session.- Comment
- A comment associated with an issue, project update, initiative update, document content, post, project, or initiative. Comments support rich text (ProseMirror), emoji reactions, and threaded replies via parentId. Comments can be created by workspace users or by external users through integrations (e.g., Slack, Intercom). Each comment belongs to exactly one parent entity.
- Comment
Connection - Comment
Edge - Comment
Payload - The result of a comment mutation.
- Contact
Payload - Return type for contact mutations.
- Create
CsvExport Report Payload - The payload returned by the createCsvExportReport mutation.
- Create
OrJoin Organization Response INTERNALResponse from creating or joining a workspace.- Custom
View - A custom view built from a saved filter, sort, and grouping configuration. Views can be personal (visible only to the owner) or shared with the entire workspace. They define which issues, projects, initiatives, or feed items are displayed and how they are organized. Views can optionally be scoped to a team, project, or initiative.
- Custom
View Connection - Custom
View Edge - Custom
View HasSubscribers Payload - The result of a custom view subscribers check.
- Custom
View Notification Subscription - A notification subscription scoped to a specific custom view. The subscriber receives notifications for events matching the custom view’s filter criteria.
- Custom
View Payload - The result of a custom view mutation.
- Custom
View Suggestion Payload - The result of a custom view suggestion query.
- Customer
- A customer organization tracked in Linear’s customer management system. Customers represent external companies or organizations whose product requests and feedback are captured as customer needs, which can be linked to issues and projects. Customers can be associated with domains, external system IDs, Slack channels, and managed by integrations such as Intercom or Salesforce.
- Customer
Connection - Customer
Edge - Customer
Need - A customer need represents a specific product request or piece of feedback from a customer. Customer needs serve as the bridge between customer feedback and engineering work by linking a customer to an issue or project, optionally with a comment or attachment providing additional context. Needs can be created manually, from integrations, or from intake sources like email.
- Customer
Need Archive Payload - A generic payload return from entity archive mutations.
- Customer
Need Connection - Customer
Need Edge - Customer
Need Notification - A notification related to a customer need (request), such as creation, resolution, or being marked as important.
- Customer
Need Payload - Return type for customer need mutations.
- Customer
Need Update Payload - Return type for customer need update mutations, including any related needs that were also updated.
- Customer
Notification - A notification related to a customer, such as being added as the customer owner.
- Customer
Notification Subscription - A notification subscription scoped to a specific customer. The subscriber receives notifications for events related to this customer, such as new customer needs or ownership changes.
- Customer
Payload - Return type for customer mutations.
- Customer
Status - A workspace-defined lifecycle status for customers (e.g., Active, Churned, Trial). Customer statuses are ordered by position and displayed with a color in the UI. Every workspace has at least one status, and a default status is assigned to new customers when none is specified.
- Customer
Status Connection - Customer
Status Edge - Customer
Status Payload - Return type for customer status mutations.
- Customer
Tier - A workspace-defined tier or segment for categorizing customers (e.g., Enterprise, Pro, Free). Customer tiers are used for prioritization and filtering, are ordered by position, and displayed with a color in the UI. Tier names are unique within a workspace.
- Customer
Tier Connection - Customer
Tier Edge - Customer
Tier Payload - Return type for customer tier mutations.
- Cycle
- A time-boxed iteration (similar to a sprint) used for planning and tracking work. Cycles belong to a team and have defined start and end dates. Issues are assigned to cycles for time-based planning, and progress is tracked via completed, in-progress, and total scope. Cycles are automatically completed when their end date passes, and uncompleted issues can be carried over to the next cycle.
- Cycle
Archive Payload - A generic payload return from entity archive mutations.
- Cycle
Connection - Cycle
Edge - Cycle
Notification Subscription - A notification subscription scoped to a specific cycle. The subscriber receives notifications for events related to issues in this cycle.
- Cycle
Payload - The payload returned by cycle mutations.
- Dashboard
InternalA configurable dashboard composed of widgets that display analytics, metrics, and insights. Dashboards can be personal or shared with the workspace, and optionally scoped to one or more teams. Each dashboard contains a set of widget configurations that define what data is visualized.- Delete
Payload - A generic payload return from entity deletion mutations.
- Document
- A rich-text document that lives within a project, initiative, team, issue, release, or cycle. Documents support collaborative editing via ProseMirror/Yjs and store their content in a separate DocumentContent entity. Each document is associated with exactly one parent entity.
- Document
Archive Payload - A generic payload return from entity archive mutations.
- Document
Connection - Document
Content - The rich-text content body of a document, issue, project, initiative, project milestone, pull request, release note, AI prompt rules, or welcome message. Content is stored as a base64-encoded Yjs state and can be converted to Markdown or ProseMirror JSON. Each DocumentContent belongs to exactly one parent entity and supports real-time collaborative editing.
- Document
Content Draft - A draft revision of document content, pending user review. Each user can have at most one draft per document content. Drafts are seeded from the live document state and stored as base64-encoded Yjs state updates, allowing independent editing without affecting the published document until the user explicitly applies their changes.
- Document
Content History Payload - Document
Content History Type - Document
Edge - Document
Notification - A notification related to a document, such as comments, mentions, content changes, or document lifecycle events.
- Document
Payload - The result of a document mutation.
- Document
Search Payload - Document
Search Result - Document
Search Result Edge - Draft
- A general-purpose draft for unsaved content. Drafts store in-progress text for comments, project updates, initiative updates, posts, pull request comments, and customer needs. Each draft belongs to a user and is associated with exactly one parent entity. Drafts are automatically deleted when the user publishes the corresponding comment or update.
- Draft
Connection - Draft
Edge - Email
Intake Address - An email address that creates Linear issues when emails are sent to it. Email intake addresses can be scoped to a specific team or issue template, and support configurable auto-reply messages for issue creation, completion, and cancellation events. They can also be configured for the Asks web form feature, enabling external users to submit requests via email.
- Email
Intake Address Payload - The result of an email intake address mutation.
- Email
Unsubscribe Payload - The result of an email unsubscribe mutation.
- Email
User Account Auth Challenge Response - Emoji
- A custom emoji defined in the workspace. Custom emojis are uploaded by users and can be used in reactions and other places where standard emojis are supported. Each emoji has a unique name within the workspace.
- Emoji
Connection - Emoji
Edge - Emoji
Payload - The result of a custom emoji mutation.
- Entity
External Link - An external link attached to a Linear entity such as an initiative, project, team, release, or cycle. External links provide a way to reference related resources outside of Linear (e.g., documentation, design files, dashboards) directly from the entity’s resources section. Each link has a URL, display label, and sort order within its parent entity.
- Entity
External Link Connection - Entity
External Link Edge - Entity
External Link Payload - The result of an entity external link mutation.
- Event
Tracking Payload - External
Entity Info - Information about an entity in an external system that is linked to a Linear entity. Provides the external ID, the service it belongs to, and optional service-specific metadata.
- External
Entity Info Github Metadata - Metadata about the external GitHub entity.
- External
Entity Info Jira Metadata - Metadata about the external Jira entity.
- External
Entity Slack Metadata - Metadata about the external Slack entity.
- External
User - An external user who interacts with Linear through an integrated external service (such as Slack, Jira, GitHub, GitLab, Salesforce, or Microsoft Teams) but does not have a Linear account. External users can create issues, post comments, and add reactions from their respective platforms. They are identified by service-specific user IDs and may optionally have an email address. External users are scoped to a single workspace.
- External
User Connection - External
User Edge - Facet
- A facet representing a join between entities. Facets connect a custom view to an owning entity such as a project, initiative, team page, workspace page, or user feed. They control the order of views within their parent via the sortOrder field. Exactly one source entity and one target entity must be set.
- Facet
Connection - Facet
Edge - Favorite
- A user’s bookmarked item that appears in their sidebar for quick access. Favorites can reference various entity types including issues, projects, cycles, views, documents, initiatives, labels, users, customers, dashboards, and pull requests. Favorites can be organized into folders and ordered by the user. Each favorite is owned by a single user and links to exactly one target entity (or is a folder containing other favorites).
- Favorite
Connection - Favorite
Edge - Favorite
Payload - Return type for favorite mutations.
- Feed
Item InternalAn item in a user’s activity feed. Feed items represent project updates, initiative updates, or posts that appear in a user’s personalized feed based on their team memberships and feed subscriptions. Each feed item references exactly one content entity. Feed items older than 6 months are automatically archived.- Feed
Item Connection - Feed
Item Edge - Fetch
Data Payload - The result of a data fetch query using natural language.
- File
Upload Delete Payload - Front
Attachment Payload - The result of a Front attachment mutation.
- GitAutomation
State - A Git automation rule that automatically transitions issues to a specified workflow state when a Git event occurs (e.g., when a PR is opened, move the linked issue to ‘In Review’). Each rule is scoped to a team and optionally to a specific target branch. When no target branch is specified, the rule acts as the default for all branches. Target-branch-specific rules override the defaults.
- GitAutomation
State Connection - GitAutomation
State Edge - GitAutomation
State Payload - The result of a git automation state mutation.
- GitAutomation
Target Branch - A target branch definition used by Git automation rules to scope automations to specific branches. The branch can be specified as an exact name (e.g., ‘main’) or as a regular expression pattern (e.g., ‘release/.*’). Each target branch belongs to a team and can have multiple automation rules associated with it, which override the team’s default automation rules when a PR targets a matching branch.
- GitAutomation
Target Branch Payload - The result of a git automation target branch mutation.
- GitHub
Commit Integration Payload - GitHub
Enterprise Server Install Verification Payload - GitHub
Enterprise Server Payload - GitLab
Integration Create Payload - GitLab
Test Connection Payload - Identity
Provider - A SAML/SSO or web forms identity provider configuration for a workspace. Identity providers enable single sign-on authentication via SAML 2.0 and can optionally support SCIM for automated user provisioning and group-based role mapping. Each workspace can have a default general-purpose identity provider and additional web forms identity providers for Asks web authentication.
- Image
Upload From UrlPayload - Initiative
- An initiative is a high-level strategic grouping of projects toward a business goal. Initiatives can contain multiple projects, have their own status updates and health tracking, and can be organized hierarchically with parent-child relationships.
- Initiative
Archive Payload - A generic payload return from entity archive mutations.
- Initiative
Connection - Initiative
Edge - Initiative
History - A history record associated with an initiative. Tracks changes to initiative properties such as name, status, owner, target date, icon, color, and parent-child relationships over time.
- Initiative
History Connection - Initiative
History Edge - Initiative
Notification - A notification related to an initiative, such as being added as owner, initiative updates, comments, or mentions.
- Initiative
Notification Subscription - A notification subscription scoped to a specific initiative. The subscriber receives notifications for events related to this initiative, such as updates, comments, and ownership changes.
- Initiative
Payload - The payload returned by the initiative mutations.
- Initiative
Relation - A parent-child relation between two initiatives, forming a hierarchy. The initiative field is the parent and relatedInitiative is the child. Cycles and excessive nesting depth are prevented.
- Initiative
Relation Connection - Initiative
Relation Edge - Initiative
Relation Payload - The result of an initiative relation mutation.
- Initiative
ToProject - The join entity linking a project to an initiative. A project can only appear once in an initiative hierarchy – it cannot be on both an initiative and one of its ancestor or descendant initiatives.
- Initiative
ToProject Connection - Initiative
ToProject Edge - Initiative
ToProject Payload - The result of an initiative-to-project mutation.
- Initiative
Update - A status update posted to an initiative. Initiative updates communicate progress, health, and blockers to stakeholders. Each update captures the initiative’s health at the time of writing and includes a rich-text body with the update content.
- Initiative
Update Archive Payload - A generic payload return from entity archive mutations.
- Initiative
Update Connection - Initiative
Update Edge - Initiative
Update Payload - The result of an initiative update mutation.
- Initiative
Update Reminder Payload - The result of an initiative update reminder mutation.
- Integration
- An integration with an external service. Integrations connect Linear to tools like Slack, GitHub, GitLab, Jira, Figma, Sentry, Zendesk, Intercom, Front, PagerDuty, Opsgenie, Google Sheets, Microsoft Teams, Discord, Salesforce, and others. Each integration record represents a single configured connection, scoped to a workspace and optionally to a specific team, project, initiative, or custom view. Personal integrations (e.g., Slack Personal, Jira Personal, GitHub Personal) are scoped to the user who created them.
- Integration
Connection - Integration
Edge - Integration
HasScopes Payload - Integration
Payload - Integration
Request Payload - The result of an integration request mutation.
- Integration
Slack Workspace Name Payload - Integration
Template - A connection between a template and an integration. This join entity links Linear issue templates to integrations so that external systems (e.g., Slack Asks channels) can use specific templates when creating issues. Each record optionally includes a foreign entity ID to scope the template to a specific external resource, such as a particular Slack channel.
- Integration
Template Connection - Integration
Template Edge - Integration
Template Payload - The result of an integration template mutation.
- Integrations
Settings - The configuration of all integrations for different entities. Controls Slack notification preferences for a specific team, project, initiative, or custom view. Exactly one of teamId, projectId, customViewId, or initiativeId must be set, determining which entity these integration settings apply to.
- Integrations
Settings Payload - Issue
- An issue is the core work item in Linear. Issues belong to a team, have a workflow status, can be assigned to users, carry a priority level, and can be organized into projects and cycles. Issues support sub-issues (parent-child hierarchy up to 10 levels deep), labels, due dates, estimates, and SLA tracking. They can also be linked to other issues via relations, attached to releases, and tracked through their full history of changes.
- Issue
Archive Payload - A generic payload return from entity archive mutations.
- Issue
Batch Payload - The result of a batch issue mutation, containing the updated issues and a success indicator.
- Issue
Connection - Issue
Draft InternalA draft issue that has not yet been created as a full issue. Drafts allow users to prepare issue details (title, description, labels, assignee, etc.) before committing them. Drafts belong to a team and a creator, and support a parent-child hierarchy similar to issues. A draft can have either a parent draft or a parent issue, but not both.- Issue
Draft Connection - Issue
Draft Edge - Issue
Edge - Issue
Filter Suggestion Payload - The result of an AI-generated issue filter suggestion based on a text prompt.
- Issue
History - A record of changes to an issue. Each history entry captures one or more property changes made to an issue within a short grouping window by the same actor. History entries track changes to fields such as title, assignee, status, priority, project, cycle, labels, due date, estimate, parent issue, and more. They also record metadata about what triggered the change (e.g., a user action, workflow automation, triage rule, or integration).
- Issue
History Connection - Issue
History Edge - Issue
History Triage Rule Error - An error that occurred during triage rule execution, such as a conflicting label assignment or an invalid property value. Contains the error type and optionally the property that caused the failure.
- Issue
History Triage Rule Metadata - Metadata about a triage responsibility rule that made changes to an issue, such as auto-assigning an issue when it enters triage. Includes information about any errors that occurred during rule execution.
- Issue
History Workflow Metadata - Metadata about a workflow automation that made changes to an issue. Links the issue history entry back to the workflow definition that triggered the change, and optionally to any AI conversation involved in the automation.
- Issue
Import - An import job for data from an external service such as Jira, Asana, GitHub, Shortcut, or other project management tools. Import jobs track the full lifecycle of importing issues, labels, workflow states, and other data into a Linear workspace, including progress, status, error states, and data mapping configuration.
- Issue
Import Check Payload - The result of checking whether an import from an external service can proceed.
- Issue
Import Delete Payload - The result of deleting an issue import, containing the deleted import job and a success indicator.
- Issue
Import JqlCheck Payload - The result of validating a custom JQL query for a Jira import.
- Issue
Import Payload - The result of an issue import mutation, containing the import job and a success indicator.
- Issue
Import Sync Check Payload - The result of checking whether an issue import can be synced with its source service after import completes.
- Issue
Label - Labels that can be associated with issues. Labels help categorize and filter issues across a workspace. They can be workspace-level (shared across all teams) or team-scoped. Labels have a color for visual identification and can be organized hierarchically into groups, where a parent label acts as a group containing child labels. Labels may also be inherited from parent teams to sub-teams.
- Issue
Label Connection - Issue
Label Edge - Issue
Label Payload - The result of a label mutation, containing the created or updated label and a success indicator.
- Issue
Notification - A notification related to an issue, such as assignment, comment, mention, status change, or priority change.
- Issue
Payload - The result of an issue mutation, containing the created or updated issue and a success indicator.
- Issue
Priority Value - A mapping of an issue priority value to its human-readable label.
- Issue
Relation - A relation between two issues. Issue relations represent directional relationships such as blocking, being blocked by, relating to, or duplicating another issue. Each relation connects a source issue to a related issue with a specific type describing the nature of the relationship.
- Issue
Relation Connection - Issue
Relation Edge - Issue
Relation History Payload - Payload describing a change to an issue relation, including which issue was involved and the type of change that occurred.
- Issue
Relation Payload - The result of an issue relation mutation, containing the created or updated issue relation and a success indicator.
- Issue
Search Payload - Issue
Search Result - Issue
Search Result Edge - Issue
Shared Access - Metadata about an issue’s shared access state, including which users the issue is shared with and any field restrictions for shared-only viewers.
- Issue
State Span - A continuous period of time during which an issue remained in a specific workflow state.
- Issue
State Span Connection - Issue
State Span Edge - Issue
Suggestion InternalAn AI-generated suggestion for an issue. Suggestions can recommend related or similar issues, assignees, labels, teams, or projects. Each suggestion has a type, state (active, accepted, dismissed), and optionally associated metadata with scoring information.- Issue
Suggestion Connection - Issue
Suggestion Edge - Issue
Suggestion Metadata InternalMetadata associated with an issue suggestion, including scoring and classification information.- Issue
Title Suggestion From Customer Request Payload - Return type for AI-generated issue title suggestions based on customer request content.
- Issue
ToRelease InternalA join entity linking an issue to a release for release tracking. Each record represents an association between a single issue and a single release, along with metadata about the source of the link (e.g., which pull requests connected the issue to the release). Creating or deleting these associations automatically records the change in issue history.- Issue
ToRelease Connection - Issue
ToRelease Edge - Issue
ToRelease Payload ALPHAThe result of an issue-to-release mutation, containing the created or updated association and a success indicator.- Jira
Fetch Project Statuses Payload - Label
Notification Subscription - A notification subscription scoped to a specific issue label. The subscriber receives notifications for events related to issues with this label.
- Logout
Response - Microsoft
Teams Channel - Microsoft
Teams Channels Payload - Microsoft
Teams Team - Notification
Archive Payload - A generic payload return from entity archive mutations.
- Notification
Batch Action Payload - Return type for batch notification mutations that operate on multiple notifications at once.
- Notification
Category Preferences - A user’s fully resolved notification category preferences. Each category maps to channel preferences indicating whether mobile, desktop, email, and Slack delivery are enabled.
- Notification
Channel Preferences - A user’s resolved notification channel preferences, indicating whether each delivery channel (mobile, desktop, email, Slack) is enabled or disabled.
- Notification
Connection - Notification
Delivery Preferences - A user’s notification delivery preferences across channels. Currently only supports mobile channel delivery scheduling.
- Notification
Delivery Preferences Channel - Delivery preferences for a specific notification channel, including an optional delivery schedule that restricts when notifications are sent.
- Notification
Delivery Preferences Day - A user’s notification delivery window for a specific day of the week. Defines the time range during which notifications will be delivered.
- Notification
Delivery Preferences Schedule - A user’s weekly notification delivery schedule, defining delivery windows for each day of the week. Notifications outside these windows are held and delivered when the window opens.
- Notification
Edge - Notification
Payload - Return type for notification mutations.
- Notification
Subscription Connection - Notification
Subscription Edge - Notification
Subscription Payload - The result of a notification subscription mutation.
- Oauth
Client Approval - A request to install an OAuth client application on a workspace, along with the admin’s approval or denial response. When a user attempts to install an OAuth application that requires admin approval, an approval record is created. A workspace admin can then approve or deny the request, optionally providing a reason. The record also tracks any newly requested scopes that were added after the initial approval.
- Oauth
Client Approval Notification - A notification related to an OAuth client approval request, sent to workspace admins when an application requests access.
- Organization
- A workspace (referred to as Organization in the API). Workspaces are the root-level container for all teams, users, projects, issues, and settings. Every user belongs to at least one workspace, and all data is scoped within a workspace boundary.
- Organization
Accepted OrExpired Invite Details Payload - Organization
Cancel Delete Payload - Workspace deletion cancellation response.
- Organization
Delete Payload - Workspace deletion operation response.
- Organization
Domain - A verified email domain associated with a workspace. Domains are used for automatic team joining, SSO/SAML authentication, and controlling workspace access. Each domain has an authentication type (general or SAML) and can be verified via email or DNS.
- Organization
Domain Claim Payload INTERNALDomain claim request response.- Organization
Domain Payload INTERNALOrganization domain operation response.- Organization
Domain Simple Payload INTERNALOrganization domain operation response.- Organization
Exists Payload - Response for checking whether a workspace exists.
- Organization
Invite - A pending invitation to join the workspace, sent via email. Invites specify the role the invitee will receive and can optionally include team assignments. Invites can expire and must be accepted by the invitee to grant workspace access.
- Organization
Invite Connection - Organization
Invite Edge - Organization
Invite Full Details Payload - Organization
Invite Payload - Workspace invite operation response.
- Organization
IpRestriction INTERNALIP restriction rule for a workspace, defining allowed or blocked IP ranges.- Organization
Meta INTERNALWorkspace metadata including region and allowed authentication providers.- Organization
Payload - Workspace update operation response.
- Organization
Start Trial Payload - Workspace trial start response.
- Page
Info - Paid
Subscription - The billing subscription of a workspace. Represents an active paid plan (e.g., Basic, Business, Enterprise) backed by a Stripe subscription. If a workspace has no Subscription record, it is on the free plan. Only one active subscription per workspace is expected.
- Passkey
Login Start Response - Post
InternalA post or announcement in a team or user feed. Posts can be manually authored by users or AI-generated summaries of team activity. They support rich text content (ProseMirror), emoji reactions, threaded comments, and audio summaries. Posts are associated with either a team or a user, but not both.- Post
Notification - A notification related to a post, such as new comments or reactions.
- Project
- A project is a collection of issues working toward a shared goal. Projects have start and target dates, milestones, status tracking, and progress metrics. They can span multiple teams and be grouped under initiatives.
- Project
Archive Payload - A generic payload return from entity archive mutations.
- Project
Attachment - An attachment (link, reference, or integration data) associated with a project. Attachments are typically created by integrations and contain metadata for rendering in the client.
- Project
Attachment Connection - Project
Attachment Edge - Project
Connection - Project
Edge - Project
Filter Suggestion Payload - The result of a project filter suggestion query.
- Project
History - A history record associated with a project. Tracks changes to project properties, status, members, teams, milestones, labels, and relationships over time.
- Project
History Connection - Project
History Edge - Project
Label - A label that can be applied to projects for categorization. Project labels are workspace-level and can be organized into groups with a parent-child hierarchy. Only child labels (not group labels) can be directly applied to projects.
- Project
Label Connection - Project
Label Edge - Project
Label Payload - The result of a project label mutation.
- Project
Milestone - A milestone within a project. Milestones break a project into phases or target checkpoints, each with its own target date and set of issues. Issues can be assigned to a milestone to track progress toward that checkpoint.
- Project
Milestone Connection - Project
Milestone Edge - Project
Milestone Move Issue ToTeam - Project
Milestone Move Payload InternalThe result of a project milestone move mutation.- Project
Milestone Move Project Teams - Project
Milestone Payload - The result of a project milestone mutation.
- Project
Notification - A notification related to a project, such as being added as a member or lead, project updates, comments, or mentions on the project or its milestones.
- Project
Notification Subscription - A notification subscription scoped to a specific project. The subscriber receives notifications for events related to this project, such as updates, comments, and membership changes.
- Project
Payload - The result of a project mutation.
- Project
Relation - A dependency relation between two projects. Relations can optionally be anchored to specific milestones within each project, allowing fine-grained dependency tracking.
- Project
Relation Connection - Project
Relation Edge - Project
Relation Payload - The result of a project relation mutation.
- Project
Search Payload - Project
Search Result - Project
Search Result Edge - Project
Status - A custom project status within a workspace. Statuses are grouped by type (backlog, planned, started, paused, completed, canceled) and define the lifecycle stages a project can move through. Each workspace can customize the names and colors of its project statuses.
- Project
Status Archive Payload - A generic payload return from entity archive mutations.
- Project
Status Connection - Project
Status Count Payload - The count of projects using a specific project status.
- Project
Status Edge - Project
Status Payload - The result of a project status mutation.
- Project
Update - A status update posted to a project. Project updates communicate progress, health, and blockers to stakeholders. Each update captures the project’s health at the time of writing and includes a rich-text body with the update content.
- Project
Update Archive Payload - A generic payload return from entity archive mutations.
- Project
Update Connection - Project
Update Edge - Project
Update Payload - The result of a project update mutation.
- Project
Update Reminder Payload - The result of a project update reminder mutation.
- Pull
Request InternalA pull or merge request from a connected version control system (GitHub or GitLab). Pull requests are automatically linked to Linear issues via branch names or commit messages containing issue identifiers. They track the full lifecycle including status, reviewers, checks, and merge state, and are synced bidirectionally with the hosting provider.- Pull
Request Check ALPHAA CI/CD check or status check associated with a pull request (e.g., a GitHub Actions workflow run or a required status check).- Pull
Request Commit ALPHAA Git commit associated with a pull request, including metadata about the commit’s content and authors.- Pull
Request Merge Settings InternalMerge settings and capabilities for a pull request’s repository, including which merge methods are allowed and whether features like merge queues and auto-merge are enabled.- Pull
Request Notification - A notification related to a pull request, such as review requests, approvals, comments, check failures, or merge queue events.
- Push
Subscription - A device registration for receiving push notifications. Each PushSubscription represents a specific browser or mobile device endpoint where a user has opted in to receive real-time push notifications. A user may have multiple push subscriptions across different devices and browsers.
- Push
Subscription Payload - Return type for push subscription mutations.
- Push
Subscription Test Payload - Return type for the push subscription test query.
- Rate
Limit Payload - The current rate limit status for the authenticated entity.
- Rate
Limit Result Payload - The state of a specific rate limit type, including remaining quota and reset timing.
- Reaction
- An emoji reaction on a comment, issue, project update, initiative update, post, pull request, or pull request comment. Each reaction is associated with exactly one parent entity and is created by either a workspace user or an external user. Reactions are persisted individually but surfaced on their parent entities as aggregated reactionData.
- Reaction
Payload - The result of a reaction mutation.
- Release
InternalA release that bundles issues together for a software deployment or version. Releases belong to a release pipeline and progress through stages (e.g., planned, started, completed, canceled). Issues are associated with releases via the IssueToRelease join entity, and the release tracks lifecycle timestamps such as when it was started, completed, or canceled.- Release
Archive Payload - A generic payload return from entity archive mutations.
- Release
Connection - Release
Edge - Release
History InternalA release history record containing a batch of chronologically ordered change events for a release. Each record holds up to 30 entries, and new records are created once the current record is full and a time window has elapsed. Tracks changes to name, description, version, stage, dates, pipeline, and archive status.- Release
History Connection - Release
History Edge - Release
Note InternalA release note. The note body is stored in related document content, and the releases it covers are tracked in releaseIds.- Release
Note Connection - Release
Note Edge - Release
Note Payload ALPHAThe result of a release note mutation.- Release
Payload - The result of a release mutation, containing the release that was created or updated and a success indicator.
- Release
Pipeline InternalA release pipeline that defines a release workflow with ordered stages. Pipelines can be continuous (each sync creates a completed release) or scheduled (issues accumulate in a started release that is explicitly completed). Pipelines are associated with teams and can filter commits by file path patterns.- Release
Pipeline Archive Payload - A generic payload return from entity archive mutations.
- Release
Pipeline Connection - Release
Pipeline Edge - Release
Pipeline Payload - The result of a release pipeline mutation.
- Release
Stage InternalA stage within a release pipeline that represents a phase in the release lifecycle (e.g., Planned, In Progress, Completed, Canceled). Releases progress through stages as they move toward production. Started-type stages can be frozen to prevent new issues from being automatically synced into releases at that stage.- Release
Stage Archive Payload - A generic payload return from entity archive mutations.
- Release
Stage Connection - Release
Stage Edge - Release
Stage Payload - The result of a release stage mutation.
- Repository
Suggestion - A suggested code repository that may be relevant for implementing an issue.
- Repository
Suggestions Payload - The result of a repository suggestions query, containing the list of suggested repositories.
- Roadmap
DeprecatedA roadmap for grouping projects. Use Initiative instead, which supersedes this entity and provides richer hierarchy and tracking capabilities.- Roadmap
Archive Payload - A generic payload return from entity archive mutations.
- Roadmap
Connection - Roadmap
Edge - Roadmap
Payload - The result of a roadmap mutation.
- Roadmap
ToProject DeprecatedThe join entity linking a project to a roadmap. Use InitiativeToProject instead, which supersedes this entity.- Roadmap
ToProject Connection - Roadmap
ToProject Edge - Roadmap
ToProject Payload - The result of a roadmap-to-project mutation.
- Semantic
Search Payload - The payload returned by the semantic search query, containing the list of matching results.
- Semantic
Search Result - A reference to an entity returned by semantic search, containing its type and ID. Resolve the specific entity using the type-specific field resolvers (issue, project, initiative, document).
- SesDomain
Identity - A verified Amazon SES domain identity that enables sending emails from a custom domain. Organizations configure SES domain identities to send issue notification replies and Asks auto-replies from their own domain instead of the default Linear domain. Full verification requires DKIM signing, a custom MAIL FROM domain, and organization ownership confirmation. Multiple organizations sharing the same domain each have their own SesDomainIdentity record but share the underlying SES identity.
- SesDomain
Identity DnsRecord - A DNS record for a SES domain identity.
- Slack
Asks Team Settings - Configuration for a Linear team within a Slack Asks channel mapping. Controls whether the default Asks template is enabled for the team in a given Slack channel.
- Slack
Channel Connect Payload - Slack
Channel Name Mapping - Configuration for a Slack channel connected to Linear via Slack Asks. Maps the Slack channel ID and name to team assignments and auto-creation settings that control how issues are created from Slack messages in this channel.
- SsoUrl
From Email Response - Subscription
- Success
Payload - Summary
- An AI-generated summary of an issue. Each issue can have at most one summary. The summary content is stored as ProseMirror data and tracks its generation status and timing.
- Synced
External Thread - A comment thread that is synced with an external source such as Slack, Jira, GitHub, Salesforce, or email. Provides information about the external thread’s origin, its current sync status, and whether the user has the necessary personal integration connected to participate in the thread.
- Team
- A team is the primary organizational unit in Linear. Issues belong to teams, and each team has its own workflow states, cycles, labels, and settings. Teams can be public (visible to all workspace members) or private (visible only to team members). Teams can also have sub-teams that inherit settings from their parent.
- Team
Archive Payload - A generic payload return from entity archive mutations.
- Team
Connection - Team
Edge - Team
Membership - A join entity that defines a user’s membership in a team. Each membership record links a user to a team and tracks whether the user is a team owner. Users can be members of multiple teams, and their memberships determine which teams’ issues and resources they can access.
- Team
Membership Connection - Team
Membership Edge - Team
Membership Payload - Team membership operation response.
- Team
Notification Subscription - A notification subscription scoped to a specific team. The subscriber receives notifications for events related to issues and activity in this team.
- Team
Payload - Team operation response.
- Template
- A reusable template for creating issues, projects, or documents. Templates store pre-filled field values and content as JSON data. They can be scoped to a specific team or shared across the entire workspace. Team-scoped templates may be inherited from parent teams.
- Template
Connection - Template
Edge - Template
Payload - The result of a template mutation.
- Time
Schedule - A time-based schedule defining on-call rotations or availability windows. Schedules contain a series of time entries, each specifying a user and their active period. They can be synced from external services (such as PagerDuty or Opsgenie) via integrations, or created manually. Schedules are used by triage responsibilities to determine who should be assigned or notified when issues enter triage.
- Time
Schedule Connection - Time
Schedule Edge - Time
Schedule Entry - A single entry in a time schedule, defining a time range and the user responsible during that period.
- Time
Schedule Payload - The result of a time schedule mutation.
- Triage
Responsibility - A team’s triage responsibility configuration that defines how issues entering triage are handled. Each team can have one triage responsibility, which specifies the action to take (notify or assign) and the responsible users, determined either by a manual selection of specific users or by an on-call time schedule.
- Triage
Responsibility Connection - Triage
Responsibility Edge - Triage
Responsibility Manual Selection - Manual triage responsibility configuration specifying a set of users to assign triaged issues to, with optional round-robin rotation.
- Triage
Responsibility Payload - The result of a triage responsibility mutation.
- Upload
File - Represents a file upload destination with a pre-signed upload URL, asset URL, and required request headers for uploading to cloud storage.
- Upload
File Header - Upload
Payload - User
- A user that belongs to a workspace. Users can have different roles (admin, member, guest, or app) that determine their level of access. Users can be members of multiple teams, and can be active or deactivated. Guest users have limited access scoped to specific teams they are invited to.
- User
Admin Payload - User admin operation response.
- User
Connection - User
Edge - User
Notification Subscription - A notification subscription scoped to a specific user view. The subscriber receives notifications for events in the context of a particular user’s activity view.
- User
Payload - User operation response.
- User
Settings - Per-user settings and preferences for a workspace member. Includes notification delivery preferences, email subscription settings, notification category and channel preferences, theme configuration, and various UI preferences. Each user has exactly one UserSettings record per workspace.
- User
Settings Custom Sidebar Theme - Custom sidebar theme definition with accent, base colors and contrast.
- User
Settings Custom Theme - Custom theme definition with accent, base colors, contrast, and optional sidebar theme.
- User
Settings Flag Payload - User settings flag update response.
- User
Settings Flags Reset Payload - User settings flags reset response.
- User
Settings Payload - User settings operation response.
- User
Settings Theme - The user’s resolved theme configuration for a specific color mode and device type.
- View
Preferences - The display preferences for a view, controlling layout mode (list, board, spreadsheet), grouping, sorting, column visibility, and other visual settings. View preferences exist at two levels: organization-wide defaults and per-user overrides. The effective preferences are computed by merging both layers, with user preferences taking priority.
- View
Preferences Payload - The result of a view preferences mutation.
- View
Preferences Project Label Group Column - A label group column configuration for the project list view.
- View
Preferences Values - The computed view preferences values for a view, containing all display settings such as layout mode, grouping, sorting, field visibility, and other visual configuration. These values represent the merged result of organization defaults and user overrides.
- Webhook
- A webhook subscription that sends HTTP POST callbacks to an external URL when events occur in Linear. Webhooks can be scoped to a specific team, multiple teams, or all public teams in the organization. They support filtering by resource type (e.g., Issue, Comment, Project) and can be created either manually by users or automatically by OAuth applications. Each webhook has a signing secret for verifying payload authenticity on the recipient side.
- Webhook
Connection - Webhook
Edge - Webhook
Failure Event - A record of a failed webhook delivery attempt. Created when a webhook payload could not be successfully delivered to the destination URL, either due to an HTTP error response or a network failure. Each failure event captures the HTTP status code (if available), the response body or error message, and a stable execution ID that is shared across retries of the same delivery.
- Webhook
Payload - The result of a webhook mutation.
- Webhook
Rotate Secret Payload - The result of a webhook secret rotation mutation.
- Welcome
Message - A welcome message configuration for the workspace. When enabled, new users joining the workspace receive a notification with this message in their inbox. Each workspace has at most one welcome message. The message body is stored in a related DocumentContent entity.
- Welcome
Message Notification - A notification containing a workspace welcome message, sent to newly joined users.
- Workflow
Definition - An automation workflow definition that executes a set of activities when triggered by specific events. Workflows can be scoped to a team, project, cycle, label, custom view, initiative, or user context. They are triggered by entity changes (e.g., issue status change, new comment) and can include conditions that filter which events actually execute the workflow. Activities define the actions taken, such as updating issue properties, sending notifications, or posting to Slack.
- Workflow
State - A state in a team’s workflow, representing an issue status such as Triage, Backlog, Todo, In Progress, In Review, Done, or Canceled. Each team has its own set of workflow states that define the progression of issues through the team’s process. Workflow states have a type that categorizes them (triage, backlog, unstarted, started, completed, canceled), a position that determines their display order, and a color for visual identification. States can be inherited from parent teams to sub-teams.
- Workflow
State Archive Payload - A generic payload return from entity archive mutations.
- Workflow
State Connection - Workflow
State Edge - Workflow
State Payload - The result of a workflow state mutation, containing the created or updated state and a success indicator.