Issue Activity
Read the Issue timeline for comments, property changes, lifecycle events, and Team moves.
Issue Activity is the timeline on Issue detail. It brings discussion and durable Issue history into one place without replacing Linear, Notion, artefact reviews, baselines, or requirements evidence.
Open an Issue, then use the Activity area above the Issue properties drawer.
What appears in Activity
Issue Activity can include:
- Top-level comments and threaded replies.
- Resolved and reopened comment threads.
- Reactions on comments.
- Title, status, priority, label, Feature, assignment, lifecycle, and Team move events.
- Relation events for related, blocked-by, blocking, create-related saves, blocker removal, and resolved-blocker conversion.
- Deleted comment placeholders that keep replies readable.
- Display-safe private Team and direct-share references.
Issue Activity uses the shared Activity system, so comments, reactions, subscriptions, and realtime refresh follow the same durable model used by other Activity-bearing objects.
The first row is one creation event. Initial status, priority, assignee, Feature, Feature Phase, labels, due date, estimate, cycle, and relations are retained in the creation snapshot rather than listed as changes made after the Issue was created. Synchronous cycle automation caused by the initial due date is folded there too. When an Issue is created from a relation, the already-existing counterpart still records that it gained the relation; the new Issue does not show duplicate creation/relation rows. Changing any of those properties or relations later adds a normal Activity row.
Phase assignment, movement, and removal use stored event-time Phase snapshots. Feature Activity receives display-safe aggregate Phase evidence without copying a private-Team Issue title, and Phase changes create no Inbox or email notification.
Label edits appear as one semantic Activity row for the complete save, including multi-label additions and removals. Historical rows keep the label names and colors captured when the change happened, even if a label is later recolored or an archived assigned label is deleted. Older Issue label history remains readable through the same presentation without rewriting old audit rows.
Privacy behavior
Activity follows Issue access. A notification, activity row, comment mention, or subscription does not grant access to an Issue.
Private Team context stays redacted for viewers who only have direct-share access. If Team context from a move or label change is not safe to show, Integrity hides or reduces it to a display-safe reference instead of exposing private Team names, identifiers, routes, label names, label colors, label counts, or status vocabulary.
Activity is evidence, not permission. If your access changes, Activity refreshes through the same server-side Issue checks as the rest of Issue detail.
Realtime updates
Activity refreshes when other users comment, reply, react, resolve threads, subscribe, or change visible Issue properties. My Issues Activity also refreshes through user-scoped realtime wake-ups when visible Issue activity changes.