For the complete documentation index, see llms.txt. This page is also available as Markdown.

Understanding Activity Feeds

Overview

Activity feeds provide a chronological record of changes and discussion.

They support fast reviews without opening every item.

Key Concepts

  • Event: comment, status change, owner change, or field update

  • Timestamp: recorded time of the event

  • Filter: constraints for narrowing activity to a time window or event type

How It’s Used

Use activity feeds during weekly governance to validate progress signals.

Use them during handoffs to understand recent changes quickly.

Benefits

  • Faster triage of blocker and approval signals

  • Reduced status meeting overhead

  • Better continuity across delivery teams

Setup Steps

1

Open the activity feed

  1. Open a requirement, task, test case, or Artifact.

  2. Locate Activity or History.

2

Filter for signal

  1. Filter by a time window when available.

  2. Filter by event type when available.

  3. Open the source item for high-impact changes.

Best Practices

  • Standardize decision language to improve scanability.

  • Use Blocked as a high-signal status only.

  • Pair activity review with Save Views for blocked and overdue work.

Summary

Activity feeds provide fast visibility into what changed and why.

Last updated