Audit Trail

Overview

Audit Trail records what changed, when, and by whom.

It supports compliance, governance, and delivery accountability.

Key Concepts

• Event: a recorded change, such as a field update
• Actor: the Teammate or system process that made the change
• Timestamp: time the event was recorded
• Context: linked item details, such as a requirement or task

How It’s Used

Use Audit Trail during approval reviews.

Use it to resolve “what changed?” questions quickly.

Benefits

• Clear accountability for scope and status changes
• Faster investigations during delivery issues
• Stronger evidence for compliance audits

Setup Steps

1

Open an item

1. Open a requirement, task, or test case.
2. Locate the history or activity area.

2

Review change history

1. Scan for status, owner, and date changes.
2. Open details for high-impact events.

3

Capture evidence (optional)

1. Copy event details into an Artifact when required.
2. Include links back to the source item.

Best Practices

• Record rationale in comments when changing scope or approvals.
• Keep approvals inside the work item, not external threads.
• Use consistent statuses to reduce ambiguous history.

Summary

Audit Trail is the source of truth for change history.

Pair it with structured requirements and statuses for clean governance.