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

[RafaelOsiro]

Warning

This PR depends on userguide#1121 getting merged first.

Overview

Documents the anomaly history entries emitted when a scan changes an anomaly's status through Auto Resolve Anomalies or Reactivate Recurring Anomalies, attributing them to Qualytics and (for Auto Resolve) linking back to the originating scan. Also mentions assignee changes in the History events list and applies light style polish to the Description note (em-dash removal plus trailing periods).

Key Changes

• History scan attribution: new !!! note admonition under Anomaly Insights → History documenting Qualytics attribution and the scan link for Auto Resolve / Reactivate Recurring Anomalies status changes.
• Recorded events list: adds assignee changes alongside status changes, description edits, and tag updates.
• Style polish: two em-dashes removed (Description note and Unlinking a Ticket paragraph) and trailing periods added to the two bullets inside the Description note.

Pages to Test

• http://localhost:8000/anomalies/details/insights/#history — ## History paragraph mentions assignee changes; the !!! note block immediately after the history-section image documents Qualytics attribution and the scan link for Auto Resolve.
• http://localhost:8000/anomalies/details/insights/#description — bulleted note under Editing the Description reads as two sentences (no em-dash) and both bullets end with a period.
• http://localhost:8000/anomalies/details/insights/#unlinking-a-ticket — paragraph ends in two sentences (no em-dash).

[greptile-apps]

Greptile Summary

This PR documents scan-triggered anomaly status changes in the History section of the Anomaly Insights page. It adds a note attributing Auto Resolve Anomalies and Reactivate Recurring Anomalies history entries to Qualytics (with a scan link for Auto Resolve), adds assignee changes to the recorded-events list, and replaces two em-dashes with period-separated sentences for consistency.

• History section: new !!! note admonition explaining Qualytics attribution and the scan back-link for Auto Resolve entries.
• Recorded events list: assignee changes added alongside status changes, description edits, and tag updates.
• Em-dash cleanup: two em-dashes converted to separate sentences in the Description note and the Unlinking a Ticket paragraph.

Confidence Score: 4/5

Safe to merge — all changes are documentation only, with no code or configuration touched.

The change is purely additive documentation. The new admonition and updated events list are clear and internally consistent. A trailing period is missing on a changed bullet, and the adjacent unchanged bullet has the same gap — both are cosmetic and easy to fix.

docs/anomalies/details/insights.md — specifically the two bullets in the Description !!! note block that are missing trailing periods.

Important Files Changed

Filename	Overview
docs/anomalies/details/insights.md	Documentation-only update adding scan attribution note to History section, assignee changes to the recorded events list, and replacing two em-dashes with period-separated sentences. One minor missing period in a changed bullet point.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Scan Runs] --> B{Status Change Triggered?}
    B -- No --> C[No History Entry]
    B -- Yes --> D{Source}
    D -- Auto Resolve Anomalies --> E[History Entry: Attributed to Qualytics + Link to originating scan]
    D -- Reactivate Recurring Anomalies --> F[History Entry: Attributed to Qualytics, No scan link]
    D -- Manual user action --> G[History Entry: Attributed to user]

Loading

_{Reviews (1): Last reviewed commit: "docs(anomalies): note scan-triggered sta..." | Re-trigger Greptile}

[greptile-apps]

The first bullet is now two full sentences after the em-dash was replaced, but the sentence is missing a trailing period. The second bullet (unchanged) has the same issue — both bullets are inconsistent with the standard sentence-ending style used throughout the rest of the document.

Suggested change

	!!! note
	- Archived anomalies cannot be edited — restore the anomaly first if you need to modify the description
	- 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
	!!! 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.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!