Skip to content

QUA-1806: Document scan-triggered status changes in anomaly history #1122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RafaelOsiro wants to merge 2 commits into
base: main
Choose a base branch
from
+7 −4
Open

QUA-1806: Document scan-triggered status changes in anomaly history #1122

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ea52ff7
docs(anomalies): note scan-triggered status changes in history
RafaelOsiro May 19, 2026
2a2e55b
docs(anomalies): add trailing periods to Description note bullets
RafaelOsiro May 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions docs/anomalies/details/insights.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,8 +59,8 @@ Users with **Editor** permission or higher can edit the description to add addit
Only users with the **Editor** role (or higher) on the respective datastore can edit the description. For more details, see the [Team Permissions](../../settings/security/teams/team-permissions/overview.md){:target="_blank"} page.

!!! note
- Archived anomalies cannot be edited — restore the anomaly first if you need to modify the description
- All changes to the description are tracked in the **History** section, maintaining a complete audit trail of modifications
- Archived anomalies cannot be edited. Restore the anomaly first if you need to modify the description.
- All changes to the description are tracked in the **History** section, maintaining a complete audit trail of modifications.

## Failed Checks

Expand Down Expand Up @@ -242,16 +242,19 @@ Click the **View :material-arrow-top-right:** button on a linked ticket card to

### Unlinking a Ticket

Click the **Unlink :material-close-thick:** button on a linked ticket card to remove the association between the ticket and the anomaly. The ticket itself remains in the external system — only the link in Qualytics is removed.
Click the **Unlink :material-close-thick:** button on a linked ticket card to remove the association between the ticket and the anomaly. The ticket itself remains in the external system. Only the link in Qualytics is removed.

![tickets-unlink-button](../../assets/anomalies/details/insights/tickets-unlink-button.png)

## History

The **History** section provides a chronological log of all actions taken on the anomaly. It automatically records system events such as anomaly creation, duplicate identification based on fingerprint matching, status changes, description edits, and tag updates. Each entry includes the user or system that performed the action and a timestamp.
The **History** section provides a chronological log of all actions taken on the anomaly. It automatically records system events such as anomaly creation, duplicate identification based on fingerprint matching, status changes, description edits, assignee changes, and tag updates. Each entry includes the user or system that performed the action and a timestamp.

![history-section](../../assets/anomalies/details/insights/history-section.png)

!!! note
When a scan changes an anomaly's status through **Auto Resolve Anomalies** or **Reactivate Recurring Anomalies**, the history entry is attributed to **Qualytics**. Auto Resolve entries also link back to the scan that performed the action.

!!! warning
Comments cannot be added, edited, or deleted when an anomaly is archived **(Resolved, Duplicate, Invalid, or Discarded)**. Restore the anomaly first to enable commenting.

Expand Down
Loading