diff --git a/TODO-documentation.md b/TODO-documentation.md index 305f103..83d5d02 100644 --- a/TODO-documentation.md +++ b/TODO-documentation.md @@ -3,7 +3,7 @@ **Branch:** `v20260207-02-wiki-documentation` **Date Started:** 2026-02-07 **Date Updated:** 2026-02-08 -**Status:** In Progress - 14 of 33 pages complete +**Status:** In Progress - 19 of 33 pages complete --- @@ -42,6 +42,13 @@ - ✅ Mail Parsing - ✅ Auto-Import Configuration +**Phase 3: Backup Review (5/5 pages - COMPLETE)** +- ✅ Approving Backups +- ✅ Daily Jobs View +- ✅ Run Checks Modal +- ✅ Overrides & Exceptions +- ✅ Remarks & Tickets + ### Screenshots Added (10 total) 1. user-management.png - User role checkboxes 2. user-settings.png - Password change form @@ -53,24 +60,17 @@ ### Remaining Work 🚧 -**Phase 3: Backup Review (0/5 pages - PLACEHOLDER)** -- ⏳ Approving Backups -- ⏳ Daily Jobs View -- ⏳ Run Checks Modal -- ⏳ Overrides & Exceptions -- ⏳ Remarks & Tickets - -**Phase 4: Advanced Features (0/17 pages - PLACEHOLDER)** +**Phase 4: Advanced Features (0/14 pages - PLACEHOLDER)** - Reports (0/4 pages) - Autotask Integration (0/4 pages) - Settings (0/6 pages) - Troubleshooting (0/3 pages) **Progress Summary:** -- ✅ 14 of 33 pages complete (42%) +- ✅ 19 of 33 pages complete (58%) - ✅ 10 screenshots added - ✅ All completed pages reviewed and corrected based on actual UI -- ⏳ 19 pages remaining (placeholders created) +- ⏳ 14 pages remaining (placeholders created) --- @@ -998,7 +998,7 @@ Add to navigation menu (after existing items): **Status:** COMPLETE **Time Spent:** ~6 hours -### Phase 3: Content Pages - Core Features 🚧 IN PROGRESS (11 of 16 complete) +### Phase 3: Content Pages - Core Features ✅ COMPLETE (16 of 16 complete) - [x] User Management (3 pages) ✅ - [x] Users & Roles - [x] Login & Authentication @@ -1013,27 +1013,26 @@ Add to navigation menu (after existing items): - [x] Inbox Management - [x] Mail Parsing - [x] Auto-Import Configuration -- [ ] Backup Review (5 pages) ⏳ - - [ ] Approving Backups - - [ ] Daily Jobs View - - [ ] Run Checks Modal - - [ ] Overrides & Exceptions - - [ ] Remarks & Tickets +- [x] Backup Review (5 pages) ✅ + - [x] Approving Backups + - [x] Daily Jobs View + - [x] Run Checks Modal + - [x] Overrides & Exceptions + - [x] Remarks & Tickets - [x] Take screenshots for core features (10 screenshots added) -**Status:** 69% complete (11/16 pages) -**Time Spent:** ~16 hours -**Remaining:** ~4 hours +**Status:** COMPLETE (16/16 pages) +**Time Spent:** ~21 hours -### Phase 4: Content Pages - Advanced Features +### Phase 4: Content Pages - Advanced Features (0/14 pages) - [ ] Reports (4 pages) - [ ] Autotask Integration (4 pages) -- [ ] Settings (6 pages) +- [ ] Settings (3 pages) - [ ] Troubleshooting (3 pages) - [ ] Take screenshots for advanced features **Estimated Complexity:** High -**Time Estimate:** 8-12 hours +**Time Estimate:** 7-10 hours ### Phase 5: Polish & Review - [ ] Proofread all content 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 ed64b6c..7bfa1b6 100644 --- a/containers/backupchecks/src/templates/documentation/backup-review/approving-backups.html +++ b/containers/backupchecks/src/templates/documentation/backup-review/approving-backups.html @@ -4,16 +4,374 @@

Approving Backups

- Learn the backup review process. + Learn the complete backup review workflow from email import to marking runs as reviewed.

+

Overview

+ +

The backup review process in BackupChecks follows a structured workflow designed to ensure all backup issues are seen and handled appropriately. This page explains the complete lifecycle from email arrival to review completion.

+ +

The Backup Review Lifecycle

+ +

The review process consists of several stages:

+ +
    +
  1. Email Import: Backup report emails arrive in your mailbox and are imported into BackupChecks
    2. +
  2. Parsing: Email content is analyzed to extract backup job information
    3. +
  3. Inbox Approval: New jobs appear in the Inbox for initial approval and customer assignment
    4. +
  4. Automatic Processing: Future emails for approved jobs are automatically processed
    5. +
  5. Daily Monitoring: Jobs appear in Daily Jobs view based on inferred schedules
    6. +
  6. Run Review: Jobs with warnings or failures are reviewed using the Run Checks modal
    7. +
  7. Issue Tracking: Problems are documented using overrides, tickets, or remarks
    8. +
  8. Mark as Reviewed: Runs are marked as reviewed after investigation
    9. +
+ +

Stage 1: Email Import & Parsing

+ +

Backup report emails are automatically imported from your configured mailbox at regular intervals (default: every 15 minutes).

+ +

What Happens

+ + + +

See Auto-Import Configuration and Mail Parsing for details.

+ +

Stage 2: Inbox Approval

+ +

When an email arrives for a job that hasn't been approved yet, it appears in the Inbox.

+ +

What Happens

+ + + +

See Inbox Management for the detailed approval process.

+ +

Stage 3: Automatic Processing

+ +

After initial approval, future emails for the same job are processed automatically:

+ +

What Happens

+ + +
- 📝 Coming Soon: - This page is under construction. Full content will be added in a future update. + 💡 First-Time Setup:
+ The Inbox approval step only happens once per job. After that, all future reports for the same job are automatically processed. This is why it's important to approve inbox emails promptly when onboarding new customers.
-

Content

+

Stage 4: Daily Monitoring

-

Detailed content will be added here in a future update.

+

Approved jobs appear in the Daily Jobs view based on inferred schedules.

+ +

What Happens

+ + + +

See Daily Jobs View for operational monitoring details.

+ +

Stage 5: Run Review

+ +

When a job shows a warning or failure, you review it using the Run Checks modal.

+ +

What Happens

+ +
    +
  1. Click on a job with a warning or failure in Daily Jobs
    2. +
  2. The Run Checks modal opens showing: + +
    3. +
  3. You investigate the issue by reviewing: + +
    4. +
  4. You determine the appropriate action (see Stage 6)
    5. +
+ +

See Run Checks Modal for detailed review instructions.

+ +

Stage 6: Issue Tracking

+ +

Based on your investigation, you choose how to handle the issue:

+ +

Option 1: Mark as Reviewed (No Action Needed)

+ +

If the issue doesn't require followup:

+ + + +

Action: Click "Mark as reviewed" in the Run Checks modal.

+ +

Option 2: Create an Override

+ +

If the issue is expected and will occur repeatedly:

+ + + +

Action: Create an override on the Overrides page. Future matching runs will automatically show as success with an override indicator.

+ +

See Overrides & Exceptions for details.

+ +

Option 3: Create a Remark

+ +

If the issue needs documentation but not formal ticket tracking:

+ + + +

Action: Click "Create Remark" in the Run Checks modal. The remark is linked to the job and shows 💬 in Daily Jobs.

+ +

Option 4: Create a Ticket

+ +

If the issue requires external followup and tracking:

+ + + +

Action: Click "Create Ticket" in the Run Checks modal. The ticket is linked to the job and shows 🎫 in Daily Jobs.

+ +

See Remarks & Tickets for tracking issues.

+ +

Stage 7: Mark as Reviewed

+ +

After handling the issue (or determining no action is needed), mark the run as reviewed:

+ +

What Happens

+ + + +
+ 💡 Success Runs Don't Need Review:
+ Successful backup runs (green badges) are automatically considered reviewed. You only need to manually review warnings and failures. +
+ +

Complete Workflow Example

+ +

Here's how a typical backup review scenario unfolds:

+ +

Day 1: New Customer Onboarding

+ +
    +
  1. 09:00: Customer's first Veeam backup email arrives
    2. +
  2. 09:15: Auto-import runs, email appears in Inbox
    3. +
  3. 09:30: You review Inbox, see new email from customer
    4. +
  4. 09:31: Click on email, verify it's legitimate, click "Approve"
    5. +
  5. 09:31: Select customer from dropdown, confirm
    6. +
  6. 09:31: Email disappears from Inbox, job is now active
    7. +
  7. 09:32: Job appears in Jobs page and Daily Jobs for today
    8. +
+ +

Day 2: First Daily Review

+ +
    +
  1. 08:00: Open Daily Jobs (defaults to today)
    2. +
  2. 08:01: Customer's job shows green "Success" - no action needed
    3. +
  3. 08:01: Continue reviewing other customers
    4. +
+ +

Day 5: Warning Appears

+ +
    +
  1. 08:00: Open Daily Jobs
    2. +
  2. 08:01: Customer's job shows yellow "Warning"
    3. +
  3. 08:02: Click on job to open Run Checks modal
    4. +
  4. 08:03: Review backup objects - one VM shows "Retry succeeded"
    5. +
  5. 08:04: Read email body - retry was successful, backup completed
    6. +
  6. 08:05: Determine: This warning is acceptable
    7. +
  7. 08:05: Click "Mark as reviewed"
    8. +
  8. 08:05: Job disappears from unreviewed list
    9. +
+ +

Day 8: Warning Repeats

+ +
    +
  1. 08:00: Open Daily Jobs
    2. +
  2. 08:01: Same customer job shows yellow "Warning" again
    3. +
  3. 08:02: Open Run Checks modal - same "Retry succeeded" warning
    4. +
  4. 08:03: Decide: This will keep happening, create an override
    5. +
  5. 08:05: Go to Overrides page
    6. +
  6. 08:06: Create object-level override: + +
    7. +
  7. 08:07: Return to Daily Jobs - job now shows green with small override badge
    8. +
  8. 08:08: Mark the run as reviewed (still need to review once after override created)
    9. +
+ +

Day 12: Failure Occurs

+ +
    +
  1. 08:00: Open Daily Jobs
    2. +
  2. 08:01: Customer job shows red "Failed"
    3. +
  3. 08:02: Open Run Checks modal
    4. +
  4. 08:03: Review objects - one VM shows "Disk full"
    5. +
  5. 08:04: Determine: Customer needs to free up space
    6. +
  6. 08:05: Click "Create Ticket"
    7. +
  7. 08:06: Fill in ticket: + +
    8. +
  8. 08:07: Create PSA ticket externally (or use Autotask integration)
    9. +
  9. 08:08: Mark run as reviewed
    10. +
  10. 08:08: Job now shows 🎫 in Daily Jobs, indicating tracked issue
    11. +
+ +

Day 15: Issue Resolved

+ +
    +
  1. 08:00: Open Daily Jobs
    2. +
  2. 08:01: Customer job shows green "Success" with 🎫 indicator
    3. +
  3. 08:02: Open Run Checks modal - confirm success for 2+ days
    4. +
  4. 08:03: Go to Tickets page
    5. +
  5. 08:04: Find ticket CUST-789, click "Resolve"
    6. +
  6. 08:05: 🎫 indicator disappears from Daily Jobs
    7. +
+ +

Best Practices

+ + + +

Role-Based Review Workflow

+ +

Operator Workflow

+ +
    +
  1. Review Daily Jobs for warnings and failures
    2. +
  2. Open Run Checks modal for each issue
    3. +
  3. Create tickets, remarks, or overrides as needed
    4. +
  4. Mark runs as reviewed after handling
    5. +
  5. Cannot unmark reviewed runs or delete overrides
    6. +
+ +

Admin Workflow

+ +
    +
  1. Same as Operator, plus:
    2. +
  2. Can view reviewed runs and review timestamps
    3. +
  3. Can unmark reviewed runs if re-investigation is needed
    4. +
  4. Can delete overrides and tickets
    5. +
  5. Monitors overall system health and team review performance
    6. +
+ +

Viewer Workflow

+ +
    +
  1. View Daily Jobs to see backup status
    2. +
  2. Cannot open Run Checks modal
    3. +
  3. Cannot create tickets, remarks, or overrides
    4. +
  4. Cannot mark runs as reviewed
    5. +
  5. Read-only access for reporting and visibility
    6. +
+ +

Performance Tips

+ + + +

Next Steps

+ + {% endblock %} diff --git a/containers/backupchecks/src/templates/documentation/backup-review/daily-jobs.html b/containers/backupchecks/src/templates/documentation/backup-review/daily-jobs.html index 4dbe464..783d158 100644 --- a/containers/backupchecks/src/templates/documentation/backup-review/daily-jobs.html +++ b/containers/backupchecks/src/templates/documentation/backup-review/daily-jobs.html @@ -4,16 +4,308 @@

Daily Jobs View

- View jobs expected to run today. + Monitor backup jobs expected to run on a specific date, with smart schedule inference and status tracking.

+

Overview

+ +

The Daily Jobs view is the primary operational dashboard for monitoring backup operations. It displays all backup jobs expected to run on a selected date, based on intelligent schedule inference from historical run patterns.

+ +

Key features:

+ + + +

Accessing Daily Jobs

+ +

To access the Daily Jobs view:

+ +
    +
  1. Navigate to Daily Jobs in the main navigation menu
    2. +
  2. Available to Admin, Operator, and Viewer roles
    3. +
  3. The view defaults to today's date in your configured timezone
    4. +
+ +

Date Selection

+ +

At the top of the page, you can select which date to view:

+ + +
- 📝 Coming Soon: - This page is under construction. Full content will be added in a future update. + 💡 Timezone:
+ Dates are displayed in your configured timezone (set in Settings). Job schedules are inferred based on when jobs historically ran in that timezone.
-

Content

+

Job Table Columns

-

Detailed content will be added here in a future update.

+

The Daily Jobs table displays the following columns:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ColumnDescription
CustomerCustomer name the job belongs to
Backup softwareBackup product (e.g., Veeam, Synology, NAKIVO)
Backup typeJob type (e.g., Backup Job, Replication Job)
Job nameName of the backup job
ScheduleInferred schedule pattern (e.g., "Daily", "Weekly: Mon Wed Fri", "Monthly: 1st, 15th")
Last runTimestamp of the most recent job run
StatusCurrent status indicator (Success, Warning, Failed, Missed, Expected)
ReviewedCheckmark if the job has been reviewed (only for non-success statuses)
+ +
+ 💡 Admin-Only Column:
+ The Reviewed column is only visible to users with the Admin role. Operators and Viewers cannot see review status in the Daily Jobs table. +
+ +

Status Indicators

+ +

Each job displays a status badge indicating its current state:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
StatusBadge ColorMeaning
SuccessGreenJob completed successfully with no warnings or errors
WarningYellowJob completed but with warnings (e.g., retry succeeded, partial backup)
FailedRedJob failed and did not complete successfully
MissedGrayJob was expected to run on this date but no run was detected
ExpectedBlueJob is expected to run later today (for future dates or today before the job runs)
+ +

Schedule Inference

+ +

BackupChecks automatically infers backup job schedules by analyzing historical run patterns. This eliminates the need to manually configure schedules for each job.

+ +

How Schedule Inference Works

+ +

The system examines the past 60 days of job runs to detect patterns:

+ + + +

Schedule Display

+ +

In the Schedule column, you'll see:

+ + + +
+ 💡 Learning Period:
+ Schedule inference requires at least 10-14 days of historical runs to detect patterns accurately. Newly approved jobs may show "-" or "Irregular" until enough data is collected. +
+ +

Override Badges

+ +

Jobs with active overrides display a small badge next to the job name. Overrides are used to handle known issues or exceptions (e.g., "treated as success due to known warning").

+ +

To view override details:

+ +
    +
  1. Look for jobs with override badges in the Daily Jobs table
    2. +
  2. Click on the job row to open the Run Checks modal (see next section)
    3. +
  3. The modal will show which overrides are applied to the job run
    4. +
+ +

Ticket and Remark Indicators

+ +

Jobs linked to active tickets or remarks display indicator icons:

+ + + +

These indicators help you quickly identify jobs with known issues or ongoing investigations.

+ +

Viewing Job Details

+ +

To view detailed information about a job run:

+ +
    +
  1. Click on any job row in the Daily Jobs table
    2. +
  2. The Run Checks modal opens, showing: + +
    3. +
+ +

See Run Checks Modal for detailed information about reviewing job runs.

+ +

Reviewing Jobs

+ +

For jobs with warnings or failures, you can mark them as reviewed after investigating:

+ +
    +
  1. Click on the job row to open the Run Checks modal
    2. +
  2. Review the job details, objects, and any error messages
    3. +
  3. Click Mark as reviewed to acknowledge you've investigated the issue
    4. +
  4. The job is marked as reviewed and removed from the unreviewed list
    5. +
+ +
+ 💡 Review Workflow:
+ Only jobs with warnings or failures need to be reviewed. Successful jobs are automatically considered reviewed. The Run Checks workflow is designed to help you quickly triage and acknowledge known issues. +
+ +

Common Workflows

+ +

Morning Backup Review

+ +
    +
  1. Open Daily Jobs (defaults to today's date)
    2. +
  2. Review the status column for any red (Failed) or yellow (Warning) badges
    3. +
  3. Click on jobs with issues to open the Run Checks modal
    4. +
  4. Investigate the failure/warning details and backup objects
    5. +
  5. Create a ticket or remark if followup is needed, or mark as reviewed if it's a known issue
    6. +
  6. Repeat for all jobs with issues
    7. +
+ +

Checking Previous Day's Jobs

+ +
    +
  1. Open Daily Jobs
    2. +
  2. Click the Previous button to go back one day
    3. +
  3. Review jobs that ran yesterday
    4. +
  4. Look for "Missed" status - jobs that were expected but didn't run
    5. +
+ +

Identifying Schedule Changes

+ +
    +
  1. Notice a job appearing on an unexpected day
    2. +
  2. Check the Schedule column to see the inferred pattern
    3. +
  3. If the schedule changed recently, it may take 10-14 days for the system to detect the new pattern
    4. +
  4. Contact the customer if a job unexpectedly stops appearing on expected days
    5. +
+ +

Best Practices

+ + + +

Troubleshooting

+ +

Job Not Appearing in Daily Jobs

+ +

If a job doesn't appear on a date when you expected it:

+ + + +

Schedule Shows "Irregular" or "-"

+ + + +

Job Shows "Missed" but Actually Ran

+ + + +

Next Steps

+ + {% endblock %} diff --git a/containers/backupchecks/src/templates/documentation/backup-review/overrides.html b/containers/backupchecks/src/templates/documentation/backup-review/overrides.html index be93c39..6d040cb 100644 --- a/containers/backupchecks/src/templates/documentation/backup-review/overrides.html +++ b/containers/backupchecks/src/templates/documentation/backup-review/overrides.html @@ -4,16 +4,368 @@

Overrides & Exceptions

- Configure override rules for special cases. + Configure override rules to automatically handle known issues, expected warnings, and special backup scenarios.

+

Overview

+ +

Overrides are rules that modify how BackupChecks interprets backup job results. They allow you to handle known issues or expected warnings without manually reviewing every occurrence.

+ +

Common use cases:

+ + + +

Accessing Overrides

+ +

To manage overrides:

+ +
    +
  1. Navigate to Overrides in the main navigation menu
    2. +
  2. Available to Admin, Operator, and Viewer roles
    3. +
  3. Viewers can see override rules but cannot create, edit, or delete them
    4. +
  4. Operators can create and edit overrides, but cannot delete them
    5. +
  5. Admins have full access to all override operations
    6. +
+ +

Override Levels

+ +

Overrides can be created at two levels:

+ +

1. Global Override

+ +

Applies to all jobs matching specific criteria:

+ + + +

Global overrides are useful for handling issues that affect multiple jobs across multiple customers.

+ +

2. Object-Level Override

+ +

Applies to a specific job or specific object within a job:

+ + + +

Object-level overrides are more precise and are checked before global overrides.

+ +

Override Match Criteria

+ +

In addition to level (global or object), overrides can match specific conditions:

+ +

Status Match

+ +

Match only runs with a specific status:

+ + + +

Most overrides match "Warning" or "Failed" to handle known issues with those statuses.

+ +

Error Text Match

+ +

Match based on error or warning message content:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Match TypeDescriptionExample
ContainsError message contains the specified text (case-insensitive)"Retry" matches "Backup retry succeeded"
ExactError message exactly matches the specified text"Retry succeeded" only matches that exact phrase
Starts withError message starts with the specified text"Retry" matches "Retry succeeded" but not "Backup retry"
Ends withError message ends with the specified text"succeeded" matches "Retry succeeded"
+ +

Leave the error text field blank to match any error message (or no error message).

+ +

Override Actions

+ +

Treat as Success

+ +

The primary action for overrides is Treat as success (enabled by default):

+ + + +

This allows you to visually differentiate between unexpected problems (red/yellow) and known issues (green with override badge).

+ +

Override Time Windows

+ +

Overrides can be time-limited using the From and Until fields:

+ +

From Date (Start Date)

+ + + +

Until Date (End Date)

+ + +
- 📝 Coming Soon: - This page is under construction. Full content will be added in a future update. + 💡 Retroactive Application:
+ When you create an override without a start date, it is applied retroactively to existing unreviewed runs. This means jobs that match the override will immediately show the "Treat as success" status in Daily Jobs, even if they ran before the override was created.
-

Content

+

Creating an Override

-

Detailed content will be added here in a future update.

+

To create a new override:

+ +
    +
  1. Navigate to the Overrides page
    2. +
  2. Fill in the "Add override" form at the top: + +
    3. +
  3. Click Save override
    4. +
  4. The override is immediately applied to matching job runs
    5. +
+ +
+ 💡 Always Add Comments:
+ Use the Comment field to document ticket numbers, reasons, or planned resolution dates. This helps other operators understand why the override exists and when it should be removed. +
+ +

Managing Existing Overrides

+ +

The "Existing overrides" table shows all configured overrides with the following columns:

+ + + +

Editing an Override

+ +
    +
  1. Click the Edit button on an override row
    2. +
  2. The "Add override" form is pre-filled with the existing values
    3. +
  3. Modify any fields
    4. +
  4. Click Save override to update
    5. +
  5. Click Cancel edit to discard changes and clear the form
    6. +
+ +

Disabling/Enabling an Override

+ +
    +
  1. Click the Disable button on an active override
    2. +
  2. The override is marked as inactive and stops affecting job runs
    3. +
  3. Click Enable to reactivate it
    4. +
+ +

Disabling is useful when you want to temporarily stop an override without deleting it (e.g., to test if an issue is resolved).

+ +

Deleting an Override (Admin Only)

+ +
    +
  1. Click the Delete button on an override row
    2. +
  2. Confirm the deletion
    3. +
  3. The override is permanently removed
    4. +
  4. Existing runs that were affected by the override remain unchanged
    5. +
+ +
+ ⚠️ Deletion is Permanent:
+ Deleted overrides cannot be recovered. If you're unsure, disable the override instead of deleting it. +
+ +

Override Evaluation Order

+ +

When a job run is evaluated, overrides are checked in the following order:

+ +
    +
  1. Object-level overrides: Most specific overrides are checked first (job + object name)
    2. +
  2. Job-level overrides: Overrides for the specific job (without object name)
    3. +
  3. Global overrides: Least specific overrides are checked last
    4. +
+ +

The first matching active override is applied. If multiple overrides match, only the most specific one takes effect.

+ +

Common Override Scenarios

+ +

Scenario 1: Veeam Retry Warnings

+ +

A Veeam backup job frequently shows warnings like "Backup retry succeeded". This is acceptable - the job ultimately succeeded.

+ +

Solution: Create an object-level override:

+ + + +

Scenario 2: Planned Maintenance Window

+ +

A customer is performing server upgrades next week. Backup failures during May 15-17 are expected.

+ +

Solution: Create a time-limited override:

+ + + +

After May 18, the override automatically expires and failures will appear normally.

+ +

Scenario 3: Known Issue with One VM

+ +

One VM in a multi-VM backup job consistently fails with "Snapshot timeout". A ticket has been created with the customer.

+ +

Solution: Create an object-specific override:

+ + + +

Other VMs in the same job will still show failures normally.

+ +

Scenario 4: Global NAKIVO Replication Warnings

+ +

All NAKIVO replication jobs show harmless warnings about "Network latency detected". This is expected for remote sites.

+ +

Solution: Create a global override:

+ + + +

Best Practices

+ + + +

Troubleshooting

+ +

Override Not Applied to Job Run

+ +

If an override doesn't appear to affect a job run:

+ + + +

Override Applying Too Broadly

+ +

If an override is affecting more jobs than intended:

+ + + +

Multiple Overrides Conflicting

+ +

Only one override is applied per run (the most specific match). If you have both global and object-level overrides that match:

+ + + +

Next Steps

+ + {% endblock %} diff --git a/containers/backupchecks/src/templates/documentation/backup-review/remarks-tickets.html b/containers/backupchecks/src/templates/documentation/backup-review/remarks-tickets.html index 9e55b70..7ee77a8 100644 --- a/containers/backupchecks/src/templates/documentation/backup-review/remarks-tickets.html +++ b/containers/backupchecks/src/templates/documentation/backup-review/remarks-tickets.html @@ -4,16 +4,424 @@

Remarks & Tickets

- Manage remarks and tickets. + Document known issues, track followup work, and link backup problems to tickets for resolution.

+

Overview

+ +

BackupChecks provides two mechanisms for documenting and tracking backup issues:

+ + + +

Both tickets and remarks can be linked to specific job runs, making it easy to track which backups are affected by known issues.

+ +

Accessing Tickets & Remarks

+ +

To view and manage tickets and remarks:

+ +
    +
  1. Navigate to Tickets in the main navigation menu
    2. +
  2. Available to Admin, Operator, and Viewer roles
    3. +
  3. Two tabs are available: + +
    4. +
+ +

Tickets

+ +

What is a Ticket?

+ +

A ticket represents an issue that requires tracking and followup. Tickets are used for:

+ + + +

Ticket Properties

+ +

Each ticket has the following properties:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
PropertyDescription
Ticket codeUnique identifier (e.g., T12345, CUST-456). Can reference an external PSA ticket number.
DescriptionBrief description of the issue
Active from dateDate when the ticket becomes active (usually the date the issue was first observed)
Start dateTimestamp when the ticket was created in BackupChecks
Resolved atTimestamp when the ticket was marked as resolved (blank if still active)
ScopesWhich backup jobs, customers, or objects this ticket affects
+ +

Creating a Ticket

+ +

Tickets can be created from several locations in the application:

+ +

From Run Checks Modal

+ +
    +
  1. Open the Run Checks modal for a job with a warning or failure
    2. +
  2. Review the job run details
    3. +
  3. Click Create Ticket (button location depends on UI implementation)
    4. +
  4. Fill in ticket details: + +
    5. +
  5. The ticket is automatically linked to the current job run
    6. +
  6. Scopes are automatically populated based on the job
    7. +
+ +

From Tickets Page

+ +

Tickets can also be created manually from the Tickets page (for issues not tied to a specific run).

+ +

Ticket Scopes

+ +

A ticket can have multiple scopes defining what it affects:

+ + + +

Scopes are used to automatically show ticket indicators (🎫) on affected jobs in the Daily Jobs view.

+ +

Viewing Ticket Details

+ +
    +
  1. Go to the Tickets page
    2. +
  2. Click View on a ticket row
    3. +
  3. The ticket detail page shows: + +
    4. +
+ +

Resolving a Ticket

+ +

When a ticket is resolved:

+ +
    +
  1. Go to the Tickets page
    2. +
  2. Click Resolve on an active ticket row (Admin/Operator only)
    3. +
  3. The ticket is marked as resolved with the current timestamp
    4. +
  4. Resolved tickets remain visible in the ticket list with a ✅ indicator
    5. +
  5. The ticket indicator (🎫) is removed from job displays
    6. +
+
- 📝 Coming Soon: - This page is under construction. Full content will be added in a future update. + 💡 Ticket Resolution:
+ Resolving a ticket does NOT delete it - it simply marks it as closed. Resolved tickets remain visible for historical reference and can be filtered using the "Status" dropdown.
-

Content

+

Linking Tickets to Additional Runs

-

Detailed content will be added here in a future update.

+

After creating a ticket, you can link it to additional job runs as they occur:

+ +
    +
  1. Open the Run Checks modal for a job run
    2. +
  2. Look for existing tickets in the ticket list (if available in UI)
    3. +
  3. Link the ticket to the current run
    4. +
+ +

This creates an audit trail showing all job runs affected by the same ticket.

+ +

Remarks

+ +

What is a Remark?

+ +

A remark is a lightweight note for documenting known issues that don't require formal ticket tracking. Remarks are used for:

+ + + +

Remark Properties

+ + + + + + + + + + + + + + + + + + + + + + + + + + +
PropertyDescription
BodyFreeform text describing the remark (no length limit)
Start dateTimestamp when the remark was created
Resolved atTimestamp when the remark was marked as resolved (blank if still active)
ScopesWhich backup jobs, customers, or objects this remark affects
+ +

Creating a Remark

+ +

Remarks are created similarly to tickets:

+ +

From Run Checks Modal

+ +
    +
  1. Open the Run Checks modal for a job run
    2. +
  2. Review the job run details
    3. +
  3. Click Create Remark
    4. +
  4. Enter remark text in the body field (supports multi-line text)
    5. +
  5. The remark is automatically linked to the current job run
    6. +
  6. Scopes are automatically populated based on the job
    7. +
+ +

From Tickets Page

+ +
    +
  1. Go to the Tickets page
    2. +
  2. Switch to the Remarks tab
    3. +
  3. Create a remark manually (if supported in UI)
    4. +
+ +

Viewing Remark Details

+ +
    +
  1. Go to the Tickets page
    2. +
  2. Switch to the Remarks tab
    3. +
  3. Click View on a remark row
    4. +
  4. The remark detail page shows: + +
    5. +
+ +

Resolving a Remark

+ +
    +
  1. Go to the Tickets page → Remarks tab
    2. +
  2. Click Resolve on an active remark row (Admin/Operator only)
    3. +
  3. The remark is marked as resolved
    4. +
  4. Resolved remarks remain visible with a ✅ indicator
    5. +
  5. The remark indicator (💬) is removed from job displays
    6. +
+ +

Filtering Tickets & Remarks

+ +

The Tickets page provides filtering options:

+ + + +

Click Filter to apply the selected criteria, or Reset to clear all filters.

+ +

Tickets vs. Remarks: When to Use Each

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Use Ticket When...Use Remark When...
Issue requires external followupIssue is internal or informational
You need to track in a PSA systemNo PSA ticket is needed
Customer action is requiredNo action is required
Issue will take days/weeks to resolveIssue is temporary (hours/days)
You need structured tracking (ticket code, formal resolution)Quick notes or documentation are sufficient
+ +

Ticket & Remark Indicators

+ +

In the Daily Jobs view and Job History pages, active tickets and remarks are indicated with icons:

+ + + +

These indicators help you quickly identify jobs with known issues during daily review.

+ +

Common Workflows

+ +

Creating a Ticket for Recurring Failure

+ +
    +
  1. Notice the same job failing in Daily Jobs for 3+ days
    2. +
  2. Click on the job to open Run Checks modal
    3. +
  3. Click Create Ticket
    4. +
  4. Enter ticket code: "CUST-12345" (from your PSA)
    5. +
  5. Description: "Daily backup fails - server disk full"
    6. +
  6. Active from date: Select the date of the first failure
    7. +
  7. Create the ticket
    8. +
  8. The job now shows 🎫 in Daily Jobs, indicating it's being tracked
    9. +
+ +

Adding a Remark for Planned Maintenance

+ +
    +
  1. Customer notifies you of planned maintenance on Friday
    2. +
  2. Go to Daily Jobs → Friday's date
    3. +
  3. Click on the customer's backup job
    4. +
  4. Click Create Remark
    5. +
  5. Body: "Planned maintenance - server will be offline from 18:00-22:00. Backup failures expected."
    6. +
  6. Create the remark
    7. +
  7. On Friday, the job shows 💬, reminding you maintenance is planned
    8. +
  8. After Friday, resolve the remark
    9. +
+ +

Resolving a Ticket After Customer Action

+ +
    +
  1. Customer confirms they've freed up disk space
    2. +
  2. Monitor Daily Jobs - backup succeeds for 2+ days
    3. +
  3. Go to Tickets page
    4. +
  4. Find the ticket for this issue
    5. +
  5. Click Resolve
    6. +
  6. The 🎫 indicator disappears from the job in Daily Jobs
    7. +
+ +

Reviewing Historical Tickets

+ +
    +
  1. Go to Tickets page
    2. +
  2. Change Status filter to "All"
    3. +
  3. Review resolved tickets to identify patterns (recurring issues, common problems)
    4. +
  4. Use this data to improve backup configurations or create preventive overrides
    5. +
+ +

Best Practices

+ + + +

Integration with Autotask

+ +

If Autotask integration is enabled, tickets can be automatically created in Autotask when backup failures occur. BackupChecks maintains internal ticket records linked to the Autotask ticket ID.

+ +

See Autotask Integration for details on PSA ticket synchronization.

+ +

Troubleshooting

+ +

Ticket Indicator Not Showing on Job

+ + + +

Cannot Create Ticket or Remark

+ + + +

Ticket Scope Affecting Wrong Jobs

+ + + +
+ ⚠️ Ticket Editing:
+ Based on the code, ticket editing is currently disabled. To modify a ticket, resolve the old ticket and create a new one with the correct information. +
+ +

Next Steps

+ + {% endblock %} 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 184fe21..a059dae 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 @@ -4,16 +4,311 @@

Run Checks Modal

- Review and mark backup runs as reviewed. + Review detailed backup job run information, examine objects and errors, and mark runs as reviewed.

+

Overview

+ +

The Run Checks modal is the detailed review interface for investigating backup job runs. It opens when you click on a job in the Daily Jobs view or Job History page.

+ +

The modal provides:

+ + + +

Opening the Run Checks Modal

+ +

The Run Checks modal can be opened from several locations:

+ + +
- 📝 Coming Soon: - This page is under construction. Full content will be added in a future update. + 💡 Role Access:
+ The Run Checks modal is available to Admin and Operator roles only. Viewers cannot open the Run Checks modal.
-

Content

+

Modal Layout

-

Detailed content will be added here in a future update.

+

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

+ +

1. Job Header

+ +

The top of the modal shows job identification:

+ + + +

2. Run List (Left Side)

+ +

A scrollable list showing recent job 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. +
+ +

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

+ +

At the top of the run details:

+ + + +

Backup Objects

+ +

A table showing individual backup items (VMs, servers, files, etc.):

+ + + + + + + + + + + + + + + + + + + + + + + + + + +
ColumnDescription
NameObject name (e.g., VM name, server name, file path)
TypeObject type (e.g., VM, Server, Repository) - if available from parser
StatusObject-level status (Success, Warning, Failed)
MessageError or warning message for this object (if any)
+ +
+ 💡 Object Availability:
+ Backup objects are only shown if the parser extracted them from the email. Not all backup software emails include object-level details. If no objects are shown, the parser didn't detect individual items in the email. +
+ +

Email Content

+ +

The original email body from the backup software is displayed in an embedded iframe:

+ + + +

Email Metadata

+ +

Above the email body, metadata is shown:

+ + + +

Download .EML

+ +

If EML storage is enabled, a download button allows you to save the original email file for external analysis or support requests.

+ +

Autotask Ticket Information

+ +

If Autotask integration is enabled and a ticket was created for this run, the modal shows:

+ + + +
+ 💡 Autotask Integration:
+ Autotask ticket information only appears if the Autotask integration is enabled in Settings and a ticket was created for this run. See Autotask Integration for details. +
+ +

Review Actions

+ +

Mark as Reviewed

+ +

For runs with warnings or failures:

+ +
    +
  1. Review the run details, backup objects, and error messages
    2. +
  2. Investigate the issue and determine if action is needed
    3. +
  3. Click the Mark as reviewed button at the top or bottom of the run details
    4. +
  4. The run is immediately marked as reviewed and disappears from the unreviewed list
    5. +
+ +

Marking a run as reviewed indicates that you have acknowledged the issue and taken appropriate action (or determined no action is needed).

+ +
+ 💡 Review Purpose:
+ The review workflow helps ensure all warnings and failures are seen by a human operator. Success runs do not need to be reviewed - they are automatically considered reviewed. +
+ +

Unmark Reviewed (Admin Only)

+ +

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

+ +
    +
  1. Enable the "Include reviewed" toggle to show reviewed runs
    2. +
  2. Select a reviewed run from the list
    3. +
  3. Click the Unmark reviewed button
    4. +
  4. The run returns to the unreviewed list
    5. +
+ +

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

+ +
+ ⚠️ Admin-Only Feature:
+ Only Admins can unmark reviewed runs. Operators can only mark runs as reviewed, not unmark them. +
+ +

Linking Tickets and Remarks

+ +

From the Run Checks modal, you can create and link tickets or remarks to document issues:

+ + + +

See Remarks & Tickets for detailed instructions.

+ +

Common Workflows

+ +

Investigating a Failed Backup

+ +
    +
  1. Open the Run Checks modal from Daily Jobs (click on the failed job row)
    2. +
  2. The most recent run is automatically selected (the failure)
    3. +
  3. Review the Backup Objects table to see which items failed
    4. +
  4. Check the Message column for error details
    5. +
  5. Scroll down to view the full email body for additional context
    6. +
  6. If the issue requires followup, create a ticket
    7. +
  7. If it's a known issue or no action is needed, mark the run as reviewed
    8. +
+ +

Comparing Multiple Runs

+ +
    +
  1. Open the Run Checks modal for a job with warnings
    2. +
  2. Enable "Include reviewed" (Admin only) to see historical runs
    3. +
  3. Click through runs in the left-side list
    4. +
  4. Compare which objects failed/succeeded across different runs
    5. +
  5. Identify patterns (e.g., same VM fails every time vs. intermittent failures)
    6. +
+ +

Reviewing Warnings with Overrides

+ +
    +
  1. Open a job with a warning badge from Daily Jobs
    2. +
  2. Notice the override indicator showing "Treated as success: [reason]"
    3. +
  3. Review the backup objects to understand why the override was created
    4. +
  4. If the override is still appropriate, mark the run as reviewed
    5. +
  5. If the override is no longer appropriate, edit or remove it on the Overrides page
    6. +
+ +

Troubleshooting Missed Jobs

+ +
    +
  1. Open a job with "Missed" status from Daily Jobs
    2. +
  2. The Run Checks modal shows recent runs
    3. +
  3. Check the timestamps to confirm the job hasn't run today
    4. +
  4. Look for patterns in historical runs (e.g., consistently misses Mondays)
    5. +
  5. Create a ticket to investigate with the customer
    6. +
  6. Mark the missed run as reviewed after creating the ticket
    7. +
+ +

Best Practices

+ + + +

Troubleshooting

+ +

No Backup Objects Shown

+ +

If the Backup Objects section is empty:

+ + + +

Email Body Shows "No message content stored"

+ + + +

Can't Mark Run as Reviewed

+ + + +

Run List Is Empty

+ + + +

Next Steps

+ + {% endblock %} diff --git a/docs/changelog-claude.md b/docs/changelog-claude.md index 5fe7b34..a7c78ff 100644 --- a/docs/changelog-claude.md +++ b/docs/changelog-claude.md @@ -10,6 +10,14 @@ This file documents all changes made to this project via Claude Code. - **Inbox Management**: Inbox overview and workflow (inbox shows ONLY unapproved emails - approved emails immediately disappear), table columns explanation (EML column shows download link, not checkmark), viewing email details with screenshot (approve-job.png), email detail modal TWO-COLUMN layout (left: metadata + action buttons + parsed objects, right: email body iframe), action buttons (Approve, Delete, Download .eml - NO Re-parse in modal), approving emails (customer selection ONLY - job name is READ-ONLY and cannot be edited), what happens after approval (email disappears from inbox, future emails auto-approved and never appear in inbox), re-parsing emails (ONLY "Re-parse all" button on inbox page - no individual re-parse), deleting emails (single and bulk delete, soft delete viewable on "Deleted Mails" page for Admins only), downloading .eml files, common workflows (new customer setup, troubleshooting unparsed emails - parsers can ONLY be created by developer, cleaning spam), best practices (verify parsed job names before approval - cannot edit during approval), removed Inbox Filters section (not in planning) - **Mail Parsing**: Parsing overview and workflow (retrieval, preprocessing, parser selection, matching, parsing, storage), parsers (viewing on separate "Parsers" page - Admin only, NOT in Settings), parser information table (removed non-existent "Enabled" column, added callout that parser list is read-only), match criteria (sender, subject, body match), supported backup software (Veeam, Synology, NAKIVO, Boxafe, Panel3, QNAP, Syncovery, 3CX, RDrive, NTFS Auditing), parser execution order, REMOVED entire "Enabling and Disabling Parsers" section (feature doesn't exist!), re-parsing emails (ONLY "Re-parse all" available, no individual re-parse), parsing workflow example, troubleshooting parsing issues (contact support - users cannot enable/disable/modify parsers), parser limitations, REMOVED "AI-powered parsing" future enhancement (not in planning, completely fabricated), best practices (removed references to testing/enabling parsers - users cannot manage parsers) - **Auto-Import Configuration**: Auto-import overview and features, enabling auto-import, import interval configuration (5/15/30/60 minutes), batch size explanation, how auto-import works (timer, check settings, authenticate, fetch, parse, auto-approve, move, log, persist, wait), auto-approval logic and conditions, when auto-approval fails, manual import (triggering, batch size 1-50), import settings summary table, monitoring import activity (audit log, inbox page, jobs/daily jobs), troubleshooting (auto-import not running, emails not auto-approved, import errors), best practices, advanced configuration (disabling temporarily, EML retention, high-volume environments) +- Completed Backup Review documentation section (5 pages): + - **Daily Jobs View**: Primary operational dashboard for monitoring backup operations, schedule inference from historical run patterns (weekly and monthly detection), status tracking (Success/Warning/Failed/Missed/Expected badges), missing job detection, override indicators with badges, ticket (🎫) and remark (💬) indicators, date selection with timezone support, job table columns (customer, backup software/type, job name, schedule, last run, status, reviewed checkmark for Admin only), schedule inference explanation (daily/weekly/monthly patterns, requires 10-14 days of data), override badges showing treated-as-success status, viewing job details via Run Checks modal, reviewing jobs (mark as reviewed for warnings/failures, successful jobs auto-reviewed), common workflows (morning review, checking previous days, identifying schedule changes), best practices (review daily, focus on failures first, watch for missed jobs, use overrides for known issues, create tickets for recurring issues), troubleshooting (job not appearing, schedule shows irregular/-, job shows missed but ran) + - **Run Checks Modal**: Detailed review interface for investigating backup job runs (opens from Daily Jobs or Job History), available to Admin and Operator roles only (not Viewer), modal layout with job header, run list (left side showing unreviewed runs by default, Admin can toggle "Include reviewed"), run details (right side showing status, backup objects table with name/type/status/message, email content in iframe with metadata and download .eml option, Autotask ticket information if integration enabled), review actions (Mark as reviewed for acknowledging issues, Unmark reviewed for Admin only), linking tickets and remarks from modal, backup objects table showing individual item statuses (objects only shown if parser extracted them), email body rendering (HTML with formatting, plain text as preformatted, sandboxed iframe for security), Autotask fields (ticket number, status, resolved origin, resolved at, deleted info with who/when), common workflows (investigating failures, comparing multiple runs, reviewing warnings with overrides, troubleshooting missed jobs), best practices (always check objects, read error messages carefully, review full email body, create tickets for recurring issues, use remarks for temporary issues, compare historical runs), troubleshooting (no backup objects shown, email body blank, can't mark as reviewed, run list is empty) + - **Overrides & Exceptions**: Override rules to automatically handle known issues and expected warnings, two override levels (global: by backup software/type affecting multiple jobs across customers, object-level: specific job or object within job checked first before global), match criteria (status match for any/success/warning/failed, error text match with contains/exact/starts_with/ends_with modes), treat as success action (enabled by default, displays green badge with override indicator instead of original status), time windows (From date optional for retroactive application to existing runs, Until date optional for permanent/temporary overrides), creating overrides (form with level/software/type/job/object/status/error match/time window/comment fields, retroactive application to unreviewed runs), managing overrides (existing overrides table showing level/scope/time/active/comment, Edit button to modify, Disable/Enable toggle, Delete for Admin only), override evaluation order (object-level first, then job-level, then global - first match wins), common scenarios with examples (Veeam retry warnings, planned maintenance windows, known issue with one VM, global NAKIVO replication warnings), best practices (start specific then generalize, always document with comments and ticket numbers, use time windows for temporary issues, review periodically, be specific with error text, test before global overrides, disable don't delete when unsure), troubleshooting (override not applied - check active status/time window/match criteria, override too broad - check global vs object level and error match type, multiple overrides conflicting - most specific wins) + - **Remarks & Tickets**: Two mechanisms for documenting issues (tickets for external followup requiring tracking, remarks for internal notes/known issues/temporary problems), accessing via Tickets page with two tabs (Tickets and Remarks tabs, filtering by status/customer/backup software/type/search), ticket properties (ticket code, description, active from date, start date, resolved at, scopes defining what it affects), creating tickets (from Run Checks modal or Tickets page, auto-linked to job run with scopes auto-populated), ticket scopes (customer/backup software/backup type/job/job run levels for automatic ticket indicators), viewing ticket details (status, code, dates, scopes list, linked runs last 20), resolving tickets (marks as resolved with timestamp, remains visible with ✅ indicator, 🎫 removed from job displays, Admin/Operator only), linking tickets to additional runs, remark properties (body freeform text, start date, resolved at, scopes), creating remarks (from Run Checks modal or Remarks tab, similar to tickets but simpler), viewing remark details (status, body, scopes, linked runs), resolving remarks (similar to tickets, 💬 removed from displays), filtering options (status active/all, customer, backup software/type, search by ticket code or job name), tickets vs remarks comparison table (when to use each), ticket/remark indicators (🎫 for active tickets, 💬 for active remarks in Daily Jobs and Job History), common workflows (creating ticket for recurring failure, adding remark for planned maintenance, resolving after customer action, reviewing historical tickets), best practices (create tickets promptly, use descriptive codes referencing PSA, set accurate active from dates, resolve promptly, use remarks for temporary issues, link to multiple runs, review monthly, use remarks for documentation), Autotask integration mention for automatic ticket creation, troubleshooting (indicator not showing - check active status and date and scope, cannot create - check role permissions, scope affecting wrong jobs - review scopes breadth), ticket editing currently disabled (resolve old and create new) + - **Approving Backups**: Complete backup review lifecycle workflow from email import to marking runs as reviewed, seven lifecycle stages (email import, parsing, inbox approval, automatic processing, daily monitoring, run review, issue tracking, mark as reviewed), Stage 1 Email Import & Parsing (auto-import from mailbox via Graph API every 15 minutes, parsers extract structured backup information), Stage 2 Inbox Approval (new job emails appear in inbox, review and approve with customer selection, creates Job and JobRun records, email disappears from inbox, future emails auto-approved), Stage 3 Automatic Processing (matching emails auto-create JobRun records, no inbox appearance, immediate Daily Jobs visibility), Stage 4 Daily Monitoring (schedule inference from patterns, status badges, overrides applied automatically, ticket/remark indicators shown), Stage 5 Run Review (click job in Daily Jobs to open Run Checks modal, investigate objects/errors/email content, determine appropriate action), Stage 6 Issue Tracking with four options (mark as reviewed for no action needed, create override for recurring expected issues, create remark for temporary/internal notes, create ticket for external followup), Stage 7 Mark as Reviewed (marks with review timestamp, disappears from unreviewed list, creates audit record, successful runs auto-reviewed), complete workflow example from Day 1 new customer onboarding through Day 15 issue resolved (showing real timestamps and decision points), role-based workflows (Operator: review/create tickets/remarks/overrides/mark reviewed, Admin: same plus view reviewed runs and unmark and delete, Viewer: read-only view Daily Jobs only), performance tips (use filters, review by exception with overrides, batch approve inbox, create global overrides for common warnings, use tickets for tracking workload, archive resolved tickets), best practices (review daily, approve inbox quickly, triage by status, use overrides for recurring warnings, create tickets for customer action, use remarks for temporary notes, always check objects, document in comments, resolve tickets promptly, monitor schedule inference) + +### Added ### Added - Added comprehensive documentation system for user onboarding and reference: