UserDrafts
The drafts of the authenticated user.
Table-Specific Information
SELECT
The add-in uses the Linear API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client-side within the add-in.- userId supports the =, !=, IN, NOT IN operators.
For example, the following queries are processed server-side:
SELECT * FROM UserDrafts LIMIT 1
Columns
| Name | Type | Description |
| userId [KEY] | String | The id of the parent User. |
| id [KEY] | String | The unique identifier of the entity. |
| createdAt | Datetime | The time at which the entity was created. |
| updatedAt | Datetime | 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. |
| archivedAt | Datetime | The time at which the entity was archived. Null if the entity has not been archived. |
| bodyData | String | The draft text content as a ProseMirror document. |
| data | String | Additional properties for the draft, such as generation metadata for AI-generated drafts, health status for project updates, or post titles. |
| updateHealth | String | The health status carried by a project update or initiative update draft. Possible values are onTrack, atRisk, or offTrack. Null for other draft types. This is a computed field derived from 'data', so clients can read the health without parsing that payload. |
| wasLocalDraft | Bool | [INTERNAL] Whether the draft was ported from a local draft. |
| anchor | String | [INTERNAL] Allows for multiple drafts per entity (currently constrained to Pull Requests). |