diff --git a/containers/backupchecks/src/templates/documentation/backup-review/approving-backups.html b/containers/backupchecks/src/templates/documentation/backup-review/approving-backups.html index 6a4c320..c79d3df 100644 --- a/containers/backupchecks/src/templates/documentation/backup-review/approving-backups.html +++ b/containers/backupchecks/src/templates/documentation/backup-review/approving-backups.html @@ -230,13 +230,13 @@

Bulk Review

-

For efficiency, you can mark multiple runs as reviewed simultaneously:

+

For efficiency, you can mark multiple jobs as reviewed simultaneously:

  1. Open the Run Checks page
  2. -
  3. Select multiple run checkboxes
  4. +
  5. Select multiple job checkboxes
  6. Click Mark selected as reviewed
  7. -
  8. All selected runs disappear from the list
  9. +
  10. All runs for all selected jobs are marked as reviewed and disappear from the list

This is especially useful for successful backups where no investigation is needed - you can quickly clear them to keep the Run Checks page empty.

diff --git a/containers/backupchecks/src/templates/documentation/backup-review/run-checks-modal.html b/containers/backupchecks/src/templates/documentation/backup-review/run-checks-modal.html index 9c2c5eb..5ade716 100644 --- a/containers/backupchecks/src/templates/documentation/backup-review/run-checks-modal.html +++ b/containers/backupchecks/src/templates/documentation/backup-review/run-checks-modal.html @@ -43,41 +43,39 @@ This is your primary daily workflow page. Open it first thing in the morning and work through all runs until the page is empty. -

Modal Layout

+

Page Layout

-

The Run Checks modal displays information in a multi-section layout:

+

The Run Checks page is organized by job, with each job showing its unreviewed runs:

-

1. Job Header

+

1. Job List

-

The top of the modal shows job identification:

+

The page displays jobs that have unreviewed runs:

-

2. Run List (Left Side)

+

2. Run Details per Job

-

A scrollable list showing recent job runs:

+

When you click on a job, you see all its unreviewed runs:

- 💡 Run List Filtering:
- By default, the run list shows only unreviewed runs for Operators. Admins can toggle "Include reviewed" to see all runs, including those already reviewed. + 💡 Review by Job:
+ Runs are grouped by job. When you mark a job as reviewed, all runs for that job are marked as reviewed simultaneously. The job then disappears from the Run Checks page. By default, only unreviewed jobs are shown. Admins can toggle "Include reviewed" to see all jobs including those already reviewed.
-

3. Run Details (Right Side)

- -

When you select a run from the list, the right side displays detailed information about that specific run.

-

Run Details Sections

Status Information

@@ -186,7 +184,7 @@
  • Review the run details, backup objects, and any error messages
  • Take action if needed (create ticket, remark, or override)
  • Click the Mark as reviewed button
  • -
  • The run is immediately marked as reviewed and disappears from the Run Checks page
  • +
  • All runs for this job are immediately marked as reviewed and the job disappears from the Run Checks page
  • Mark as Reviewed (Bulk)

    @@ -194,9 +192,9 @@

    For efficiency, especially with successful backups:

      -
    1. Select multiple run checkboxes in the Run Checks list
    2. +
    3. Select multiple job checkboxes in the Run Checks list
    4. Click Mark selected as reviewed button
    5. -
    6. All selected runs disappear from the Run Checks page
    7. +
    8. All runs for all selected jobs are marked as reviewed and disappear from the Run Checks page

    This is particularly useful for quickly clearing successful backups that don't require investigation.

    @@ -208,16 +206,16 @@

    Unmark Reviewed (Admin Only)

    -

    Admins can unmark a reviewed run if it needs to be re-investigated:

    +

    Admins can unmark a reviewed job if it needs to be re-investigated:

      -
    1. Enable the "Include reviewed" toggle to show reviewed runs
    2. -
    3. Select a reviewed run from the list
    4. +
    5. Enable the "Include reviewed" toggle to show reviewed jobs
    6. +
    7. Select a reviewed job from the list
    8. Click the Unmark reviewed button
    9. -
    10. The run returns to the unreviewed list
    11. +
    12. All runs for this job return to the unreviewed list
    -

    This is useful if new information about an issue comes to light after the run was marked as reviewed.

    +

    This is useful if new information about an issue comes to light after the job was marked as reviewed.

    ⚠️ Admin-Only Feature:
    @@ -316,16 +314,16 @@

    Run List Is Empty

    Next Steps

    diff --git a/docs/changelog-claude.md b/docs/changelog-claude.md index 1c0502f..d573c98 100644 --- a/docs/changelog-claude.md +++ b/docs/changelog-claude.md @@ -6,11 +6,11 @@ This file documents all changes made to this project via Claude Code. ### Changed - Fixed critical inaccuracies in Backup Review documentation based on user feedback: - - **Approving Backups page**: Corrected Stage 6 to emphasize ALL runs must be marked as reviewed regardless of action taken (override/ticket/remark created), added warning callout that failing to mark as reviewed leaves runs visible with wrong status next day, corrected Stage 7 to clarify successful runs MUST also be reviewed (goal is empty Run Checks page), added bulk review functionality for efficiency, completely rewrote Complete Workflow Example to focus on Run Checks page (primary daily tool) instead of Daily Jobs, updated best practices and role-based workflows to prioritize Run Checks over Daily Jobs, added performance tips for bulk review + - **Approving Backups page**: Corrected Stage 6 to emphasize ALL runs must be marked as reviewed regardless of action taken (override/ticket/remark created), added warning callout that failing to mark as reviewed leaves runs visible with wrong status next day, corrected Stage 7 to clarify successful runs MUST also be reviewed (goal is empty Run Checks page), added bulk review functionality for efficiency, completely rewrote Complete Workflow Example to focus on Run Checks page (primary daily tool) instead of Daily Jobs, updated best practices and role-based workflows to prioritize Run Checks over Daily Jobs, added performance tips for bulk review, corrected bulk review section from "select multiple run checkboxes" to "select multiple job checkboxes" to reflect per-job review mechanism - **Daily Jobs page**: Added blue "Success (Override)" status indicator to table showing runs treated as success due to active override, added callout clarifying Daily Jobs is for viewing schedules only and Run Checks is the primary operational tool (Daily Jobs may be deprecated in future), corrected page purpose from "primary operational dashboard" to schedule viewing tool - - **Run Checks Modal page**: Corrected overview to emphasize this is THE primary daily operational tool (not just detail modal), added callout that goal is completely empty page, corrected "Success Runs Don't Need Review" to "All Runs Must Be Reviewed" with explanation, added bulk review section (select multiple + mark all), updated status information to include blue badge for override-applied runs, changed access description from "modal" to "page" + - **Run Checks Modal page**: Corrected overview to emphasize this is THE primary daily operational tool (not just detail modal), added callout that goal is completely empty page, corrected "Success Runs Don't Need Review" to "All Runs Must Be Reviewed" with explanation, added bulk review section (select multiple + mark all), updated status information to include blue badge for override-applied runs, changed access description from "modal" to "page", removed non-existent "reviewed indicator" from page layout, corrected review mechanism from per-run to per-JOB (when marking a job as reviewed, ALL runs within that job are marked simultaneously), updated Mark as Reviewed section to clarify all runs for the job disappear together, corrected bulk review from "select multiple run checkboxes" to "select multiple job checkboxes", updated Unmark Reviewed section to reflect per-job unmarking, removed incorrect statement that successful runs are automatically reviewed, fixed troubleshooting section to remove false claim about successful runs not needing review - **Overrides & Exceptions page**: Updated "Treat as Success" action description to show blue badge instead of green, added visual differentiation explanation (green=genuine success, blue=override applied, yellow/red=unexpected problems) - - All changes ensure documentation accurately reflects actual workflow: Run Checks is primary tool, all runs need review (including successes), blue badges indicate overrides + - All changes ensure documentation accurately reflects actual workflow: Run Checks is primary tool, all runs need review (including successes), blue badges indicate overrides, review is per-JOB not per-run ### Added - Completed Mail & Import documentation section (4 pages):