> 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/comments-and-history.md).

# Comments and History

### Overview

Comments capture discussion and decisions.

History captures a timestamped change log for the item.

### Key Concepts

* **Comment thread**: discussion attached to the item
* **History event**: recorded change, such as status or owner update
* **Actor**: Teammate or system process that performed the change

### How It’s Used

Use comments for approvals and rationale.

Use history to validate scope, ownership, and status changes.

### Benefits

* Cleaner governance through traceable decisions
* Faster investigations during delivery issues
* Reduced duplicate work during handoffs

### Setup Steps

{% stepper %}
{% step %}

### Open comments

1. Open an item detail panel.
2. Locate the comment area.
3. Add a comment using a consistent decision pattern when applicable.
   {% endstep %}

{% step %}

### Open history

1. Locate the **History** or **Activity** area.
2. Review status, owner, and field changes.
3. Filter by time window when available.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Record decisions and rationale in the same comment.
* Link to Artifacts and related items instead of duplicating long text.
* Check history before reopening closed work.

### Summary

Comments provide context. History provides accountability.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/collaboration-and-automation/comments-and-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.