Anomaly Timeline¶

Reviewing an anomaly's timeline and comments

The Timeline is an anomaly's history and its conversation in one list. It records every change made to the anomaly, who or what made it, and when, and it holds the comments the team writes while working on it. Reading it from the bottom up tells the whole story of an anomaly, from the Scan that found it to the decision that closed it.

The same Timeline, with the same commenting, is also available on tables and files, quality checks, and check templates.

What the Timeline Records¶

Qualytics adds an entry to the Timeline for each of these events:

• The anomaly being created by a Scan.
• On the earliest anomaly with a fingerprint, each later anomaly with the same fingerprint, with its ID as a link. See Related Anomalies.
• Status changes, including acknowledging, archiving, and restoring.
• Description edits.
• Tags added or removed.
• Assignees added or removed. Self-assignment and self-unassignment are labeled as such, so it is clear when a teammate takes ownership or steps away.
• Tickets linked or unlinked. The entry shows the ticket number as a link to the ticketing system.
• Impact changes, when the anomaly's Impact is decided again.

Each entry names the user who made the change and when. A change made by Qualytics itself, such as a Scan reopening the anomaly with Reactivate Recurring Anomalies or resolving it with Auto Resolve Anomalies, is attributed to Qualytics. Auto Resolve entries link to the Scan that resolved the anomaly: hover the entry's avatar to open it. An Impact change caused by your action, such as editing the tags of a failed check, is credited to you with a Qualytics co-author badge, and to Qualytics alone otherwise.

A ticket's own status changes are shown on its card in the Tickets section and are not recorded on the Timeline. When the integration's Anomaly status sync moves the anomaly, that status change is recorded like any other. See Anomaly Tickets.

Reading a Change¶

A short change reads inline on its entry, as from <previous value> to <new value>. A long one collapses behind a View changes control instead. That happens when the two values together run past about 170 characters, or when either one contains a line break. The control shows the length before and after, such as 32 → 166 chars, and opens a panel with the From and To values. Hide closes it again. This keeps a long description edit from filling the Timeline while the full text stays one click away.

When one save changes several properties at once, they are grouped into a single entry rather than split into separate rows.

The Timeline shows the most recent activity first. Show more at the bottom loads older entries, along with the comments from the same period.

Comments¶

Comments let the team discuss an anomaly where its history is: what was checked, what was decided, and why. Every comment shows its author and when it was posted. There are two places to write one.

Comments on the Anomaly¶

A comment written in the Leave a comment field above the Timeline is about the anomaly as a whole. Anyone can Reply to it, and the replies are grouped into a thread under it that collapses into a pill such as 3 replies • last reply 20 minutes ago. Threads are one level deep: you reply to a comment, not to a reply.

Comments on a Change¶

A comment can also be attached to one Timeline entry, so a status change or a description edit always carries the reason for it. Below an entry, the control stays Comment rather than Reply: everyone who writes there adds to one running conversation about that change. Once an entry has comments, they collapse into a pill such as 2 comments • last comment 3 hours ago.

Mentions¶

Typing @ in a comment or a reply opens a list of users, filtered by name, email, or username as you type. A mentioned user becomes a highlighted chip in the comment and receives an in-app Mention notification. Opening it goes straight to the comment: the anomaly opens, the thread expands, and the comment is scrolled into view and briefly highlighted. Links pasted into a comment become clickable.

Anyone active on the platform can be mentioned, including users without access to the anomaly's datastore. They receive the notification but cannot open the anomaly, so mention the people who can act on the comment. Editing a comment notifies only the people newly added to it. See Mention Notification.

Editing and Deleting Comments¶

Only the author of a comment can edit it. The author or a user with the Admin role can delete it.

Deleting a comment that has replies leaves a placeholder reading This comment was deleted, so the replies stay visible and the thread still reads in order. The confirmation asks about it before you delete. When the last reply is deleted, the placeholder goes with it.

Comments on Archived Anomalies¶

When an anomaly is archived, its comments stay visible but become read only. No comment can be added, edited, or deleted until the anomaly is restored.

Comments and Linked Tickets¶

When the anomaly has linked tickets set to Two-way, comments written on the Timeline are also posted to them:

A comment reaches the ticket as plain text, so a mention arrives as a raw code rather than as a name, and the mentioned user is notified in Qualytics only. Replies arrive as separate comments, because tickets keep a flat list. The Timeline keeps the full thread. A mirrored comment with no Qualytics author cannot be edited in Qualytics, though an Admin can delete it.

See comment sync for Jira and ServiceNow.

Permissions¶

For every anomaly action, see Anomaly Permissions. For the steps, see the Comments how-tos.

See Also¶