Overview
Therequests table stores feature requests and user feedback items. Each request has a title, description, status, and can be associated with areas, followers, and related links.
Fields
Primary key. Auto-generated UUID for the request.
The title of the feature request.
Detailed description of the feature request.
Current status of the request. See Enums for possible values. Default:
open.Foreign key reference to
users.id. The user who created the request.Timestamp with timezone when the request was created. Default:
now().Timestamp with timezone when the request was last updated. Default:
now().URL-friendly unique identifier for the request. Must be unique.
Additional internal notes about the request.
Array of area IDs associated with this request. Default:
[].Array of external URLs related to this request. Default:
[].URL to the associated Linear issue, if any.
Array of user IDs following this request. Default:
[].Foreign key reference to another request in
requests.id. Links related requests together.Additional metadata stored as JSON.
Enums
request_status
Thestatus field uses the request_status enum with the following values:
open- Request is active and being consideredshipped- Feature has been implemented and releaseddeprioritized- Request has been deprioritized
Relationships
Belongs to
- User (creator):
requests.creator→users.id - Related Request (self-referential):
requests.relatedRequestId→requests.id
Has many
- Feedback: Multiple feedback items can reference a single request via
feedback.requestId
Indexes
Unique constraint on the
slug field.B-tree index on
creator field for faster queries by creator.B-tree index on
updatedAt field for sorting by modification time.GIN index on
areaIds array for efficient array containment queries.GIN index on
relatedLinks array for efficient array searches.GIN index on
followers array for efficient follower lookups.B-tree index on
relatedRequestId for related request queries.