# Check Timeline

Source: https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/check-details/timeline/

The **Timeline** on a check's page is the chronological record of everything that happened to the check: its creation, every change to its configuration, automatic adjustments, and the comments your team leaves along the way. It keeps a change and the reason behind it in the same place. The Timeline sits next to the Definition on the check's page. See [Check Views](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/check-details/check-views/#check-page).

Entries load as you scroll, so older ones appear without paging through the list.

> **Note: Formerly Activity and History**
>
> This section was first labeled **Activity**, then **History**. It is now the **Timeline**, as on the other assets, because it carries discussion alongside the change record.

## What the Timeline Records

Each entry shows who did what and when:

- **Creation.** The first entry records how the check was created. When Profile created it as an [AI Managed](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/ai-managed-checks/) check, the entry is attributed to **Qualytics** and links to that Profile operation: hover the entry's avatar to open it.
- **Changes.** Every saved change to the check's configuration, properties, status, or tags. When one save changes several properties, they are grouped into a single entry.
- **Importance changes.** A change to the check's [Importance](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/importance/) gets its own entry. When your action caused it, for example editing the check's tags, it is credited to you with a **Qualytics** co-author badge. Otherwise it is credited to **Qualytics** alone.

## Reviewing a Change

Short values show inline on the entry, reading `from <previous value> to <new value>`. A long change collapses behind a **View changes** control instead, so a long property never floods the Timeline. This happens when the two values together run past roughly 170 characters, or when either one contains a line break. The control reports the before and after lengths, for example `32 → 166 chars`, and expands into a panel with the **From** and **To** values. Any field can collapse this way, a rewritten description as much as a filter clause.

## Past Versions

Each entry has a **check icon** on its right side. Clicking it opens a side panel with the check's full configuration as it was at that point. The **Version At** field gives the exact date and time that version took effect.

## Comments

You can discuss the check directly on its Timeline:

- **Comment on the check.** Use the comment box above the Timeline, with the placeholder **Leave a comment (use @ to mention users)**. The comment takes its place in the Timeline, in chronological order.
- **Comment on a specific change.** Click **Comment**  below a change entry. The comment stays attached to that entry, so a threshold change carries the request it came from. Once an entry has comments, they collapse into a pill with the authors' avatars, the comment count, and when the last comment was posted.
- **Reply to a comment.** Click **Reply**  below a comment. Threads are one level deep, so you reply to a comment, not to a reply.
- **Mention a teammate.** Type `@` and pick a user from the list. They receive an in-app **Mention** notification that opens the check, expands the thread, and highlights the comment, even when it sits further back in the Timeline.

Authors can edit and delete their own comments from the options menu on the comment. Users with the **Admin** role can delete anyone's comment, and nobody can edit someone else's. Deleting a comment that already has replies leaves a placeholder reading *This comment was deleted*, so the replies stay visible.

Comments on an archived check are read-only. Existing comments stay visible and the comment controls stay on screen, but posting, editing, or deleting a comment is rejected with an error until the check is restored.

## Permissions

| Action | Minimum team permission on the datastore |
| --- | --- |
| Read the Timeline and its comments | **Reporter** |
| Post a comment, reply, or edit or delete your own comment | **Viewer** |

See [Team Permissions](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/).

## See Also

- **Check Examples**

  Scenarios that show ownership and AI Managed checks in practice.

  [Check Examples](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/examples/)
- **Check Permissions**

  Which team permissions can view, create, edit, archive, and delete checks, change owners, and edit AI Managed checks.

  [Check Permissions](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/permissions/)
- **How a Check Works**

  What a check is made of, who creates it, how AI Managed checks are generated, how a Scan evaluates it, and how its status changes.

  [How a Check Works](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/how-it-works/)
- **Authored Checks**

  What an Authored check is, who governs it, and how it differs from an AI Managed check.

  [Authored Checks](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/authored-checks/)
- **AI Managed Checks**

  What an AI Managed check is, which edits convert it to Authored, and how to go back.

  [AI Managed Checks](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/ai-managed-checks/)
- **Check Ownership**

  Who is responsible for a check, the four ways ownership changes, notifications, and filtering by owner.

  [Check Ownership](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/ownership/)
- **Check Importance**

  How much a check's failures matter, and how its tags raise or lower it.

  [Check Importance](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/importance/)
- **Impact Metrics**

  Numbers measured over a check's failed records that show how big a failure is.

  [Impact Metrics](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/impact-metrics/)
- **Dry Run**

  What a Dry Run evaluates and how to read its results, anomalies, and source records.

  [Dry Run](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/dry-run/)
- **Check Views**

  The check lists, the check page, and the side panel: how to reach each one, what it shows, and what you can do there.

  [Check Views](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/check-details/check-views/)
- **Check Anomalies**

  The anomalies a check has produced, and how to triage them from the check's page.

  [Check Anomalies](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/check-details/anomalies/)

*Last updated: November 10, 2026.*