> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/collaboration-and-automation/understanding-activity-feeds.md).

# 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

{% stepper %}
{% step %}

### Open the activity feed

1. Open a requirement, task, test case, or Artifact.
2. Locate **Activity** or **History**.
   {% endstep %}

{% step %}

### 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.
   {% endstep %}
   {% endstepper %}

### 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/collaboration-and-automation/understanding-activity-feeds.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.