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

Tracking Changes and Decisions

Use history and activity feeds to understand what changed, when, and why.

Overview

Activity tracking shows a timestamped record of updates.

Use it for audits, handoffs, and “why did this change?” moments.

Screenshot placeholder: item detail view with an Activity/History tab.

Key Concepts

  • Activity feed: chronological list of comments and changes

  • History: field-level change record (when enabled)

  • Decision pattern: consistent formatting used for approvals and rationale

How It’s Used

Use this workflow during weekly governance.

Use it during investigations and handoffs.

Benefits

  • Faster validation of progress signals

  • Better accountability for approvals

  • Reduced rework caused by missing context

Setup Steps

1

Open the item

Open the task, requirement, test case, or Project for review.

2

Open Activity / History

Look for:

  • status changes

  • assignee changes

  • field edits

  • comments and mentions

  • links added/removed (requirements ↔ tasks ↔ tests)

3

Capture the decision

When a decision appears in the thread:

  • add a short summary comment using Decision:

  • @mention the approver or owner

  • link supporting Artifacts

Best Practices

  • Put approvals in comments, not in direct messages.

  • Use consistent tags: Decision:, Approved by:, Blocked by:.

  • Summarize meeting outcomes in one comment.

Troubleshooting

I can’t see Activity or History

Possible causes:

  • feature not enabled for the Account

  • role does not have access to history

Ask an Account Admin to confirm configuration and permissions.

The history is noisy

Do this:

  • filter by user (if available)

  • filter by event type (status/assignee/comments)

  • standardize on a single “Decision” summary comment per change

Summary

Activity tracking provides the evidence layer for decisions and scope changes.

Related:

Last updated