Activity Feed
Track comments and object changes in a shared, display-safe activity timeline.
Activity is the timeline and discussion surface attached to work objects in Integrity. It keeps comments, replies, reactions, edit history, resolved threads, and system events near the object they explain instead of creating a separate project-management feed.
Where Activity appears
Activity is currently available on Issue detail, Artefact Activity, Artefact Review & Discuss, Feature health updates, and Initiative health updates. My Issues also has an Activity scope that lists active Issues connected to recent shared Activity that is visible to you.
The exact rows depend on the object:
| Surface | Activity includes |
|---|---|
| Issue detail | Comments, replies, reactions, thread resolution, subscriptions, assignment and property activity, and Team move context. |
| Artefacts | Comments, replies, reactions, resolved threads, version context, review activity, reviewer changes, link group changes, restores, and kind changes. |
| Feature and Initiative updates | Authored health updates, discussions, reactions, and semantic property activity for status, priority, people, Teams, relationships, dependencies, dates, schedules, icon colors, and labels. |
| My Issues Activity | Active Issues connected to assignment, creation, direct share, subscription, comment, reply, or reaction activity. |
Realtime and privacy
Activity updates refresh through private realtime channels. Object detail pages listen to the selected object's Activity subject, while user aggregate views such as My Issues > Activity listen to a private user wake-up that only the signed-in user can join.
Activity rows and aggregate lists always refetch through server access checks. Private Teams, restricted modules, direct-shared Issues, deleted objects, unavailable users, and hidden references render with display-safe labels instead of exposing raw titles, paths, identifiers, or Team context you cannot access.
Property events use the same visual grammar across Issue, Feature, and Initiative timelines: muted timeline chrome with a property-specific icon or changed-person avatar. Label changes are grouped into one row per save. A single visible label uses its event-time color; multiple or restricted changes use a muted label icon. Archived-label deletion keeps the historical name and color, while private Team labels appear only as a generic update to direct-shared viewers without Team access.
When you create an Issue, Feature, or Artefact, Activity starts with one creation row. Values, memberships, and relationships chosen as part of creation—and automation that runs synchronously because of those choices—are retained in the creation/version snapshot, but they are not shown as changes made after creation. If a new object is created from a relation, the already-existing related object may still show that it gained the relation. Later edits still add their own rows. This keeps the feed concise without discarding historical evidence as object schemas evolve.
Feature and Initiative date rows identify the changed start, target, or roadmap-window property and show only its resulting value. Team rows name accessible single-Team additions, removals, and replacements; larger or restricted changes use safe summaries. Member changes identify the changed person when that identity is available.
Feature Phase create, rename, target-date, reorder, delete, and aggregate Issue-assignment events use stored number/name/date/order/stage snapshots. Aggregate Feature rows never copy a private-Team Issue title, and ordinary collaborative Phase description edits remain document provenance rather than Activity noise.
Human action boundary
Integrity can use Activity as evidence for summaries and agent context, but agents do not publish comments, resolve threads, subscribe users, send notifications, or mutate object state without explicit user action.