pub struct Attachment {Show 16 fields
pub id: Option<String>,
pub created_at: Option<DateTime<Utc>>,
pub updated_at: Option<DateTime<Utc>>,
pub archived_at: Option<DateTime<Utc>>,
pub title: Option<String>,
pub subtitle: Option<String>,
pub url: Option<String>,
pub creator: Option<User>,
pub external_user_creator: Option<ExternalUser>,
pub metadata: Option<Value>,
pub source: Option<Value>,
pub source_type: Option<String>,
pub group_by_source: Option<bool>,
pub original_issue: Option<Issue>,
pub issue: Option<Issue>,
pub body_data: Option<String>,
}Expand description
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.
Fields§
§id: Option<String>The unique identifier of the entity.
created_at: Option<DateTime<Utc>>The time at which the entity was created.
updated_at: Option<DateTime<Utc>>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.
archived_at: Option<DateTime<Utc>>The time at which the entity was archived. Null if the entity has not been archived.
title: Option<String>Content for the title line in the Linear attachment widget.
subtitle: Option<String>Content for the subtitle line in the Linear attachment widget.
url: Option<String>The URL of the external resource this attachment links to. Also serves as a unique identifier for the attachment within an issue; no two attachments on the same issue can share the same URL.
creator: Option<User>The creator of the attachment.
external_user_creator: Option<ExternalUser>The non-Linear user who created the attachment.
metadata: Option<Value>Integration-specific metadata for this attachment. The schema varies by source type and may include fields such as pull request status, review counts, commit information, ticket status, or other data from the external system.
source: Option<Value>Information about the source which created the attachment.
source_type: Option<String>The source type of the attachment, derived from the source metadata. Returns the integration type (e.g., ‘github’, ‘slack’, ‘zendesk’) or ‘unknown’ if no source is set.
group_by_source: Option<bool>Whether attachments from the same source application should be visually grouped together in the Linear issue detail view.
original_issue: Option<Issue>The issue this attachment was originally created on. Null if the attachment hasn’t been moved.
issue: Option<Issue>The issue this attachment belongs to.
body_data: Option<String>The body data of the attachment, if any.
Trait Implementations§
Source§impl Clone for Attachment
impl Clone for Attachment
Source§fn clone(&self) -> Attachment
fn clone(&self) -> Attachment
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more