From f62c19ddf86a07f8276a05c23c63e1b369cf7254 Mon Sep 17 00:00:00 2001
From: Ivo Oskamp <ivooskamp@oskamp.info>
Date: Tue, 10 Feb 2026 11:26:37 +0100
Subject: [PATCH] Update Settings Maintenance test email text
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The UI text still mentioned "3 emails simulating Veeam, Synology,
and NAKIVO" but the actual behavior changed to 1 Veeam email per button.

Changes:
- Updated description: Now states "1 Veeam Backup Job email" per button
- Updated button labels: "emails (3)" → "email (1)"
- Clarified that only Veeam test emails are generated

This matches the actual implementation that was changed earlier.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
---
 containers/backupchecks/src/templates/main/settings.html | 8 ++++----
 docs/changelog-claude.md                                 | 1 +
 2 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/containers/backupchecks/src/templates/main/settings.html b/containers/backupchecks/src/templates/main/settings.html
index 2254fc6..aa79d88 100644
--- a/containers/backupchecks/src/templates/main/settings.html
+++ b/containers/backupchecks/src/templates/main/settings.html
@@ -563,16 +563,16 @@
     <div class="card h-100 border-info">
       <div class="card-header bg-info text-white">Generate test emails</div>
       <div class="card-body">
-        <p class="mb-3">Generate fixed test email sets in the inbox for testing parsers and maintenance operations. Each set contains 3 emails simulating Veeam, Synology, and NAKIVO backups.</p>
+        <p class="mb-3">Generate Veeam test emails in the inbox for testing parsers and maintenance operations. Each button creates 1 Veeam Backup Job email with the specified status.</p>
         <div class="d-flex flex-column gap-2">
           <form method="post" action="{{ url_for('main.settings_generate_test_emails', status_type='success') }}">
-            <button type="submit" class="btn btn-success w-100">Generate success emails (3)</button>
+            <button type="submit" class="btn btn-success w-100">Generate success email (1)</button>
           </form>
           <form method="post" action="{{ url_for('main.settings_generate_test_emails', status_type='warning') }}">
-            <button type="submit" class="btn btn-warning w-100">Generate warning emails (3)</button>
+            <button type="submit" class="btn btn-warning w-100">Generate warning email (1)</button>
           </form>
           <form method="post" action="{{ url_for('main.settings_generate_test_emails', status_type='error') }}">
-            <button type="submit" class="btn btn-danger w-100">Generate error emails (3)</button>
+            <button type="submit" class="btn btn-danger w-100">Generate error email (1)</button>
           </form>
         </div>
       </div>
diff --git a/docs/changelog-claude.md b/docs/changelog-claude.md
index 5b76c22..7ac0730 100644
--- a/docs/changelog-claude.md
+++ b/docs/changelog-claude.md
@@ -14,6 +14,7 @@ This file documents all changes made to this project via Claude Code.
 ### Changed
 - Added debug logging to ticket linking function to troubleshoot resolved ticket propagation issues (writes to AuditLog table with event_type "ticket_link_debug", visible on Logging page, logs EVERY run import to show whether tickets were found and their resolved_at status, uses commit instead of flush to ensure persistence) - **LATER REMOVED** after ticket system was fixed
 - Reduced test email generation from 3 emails per status to 1 email per status for simpler testing (each button now creates exactly 1 test mail instead of 3)
+- Updated Settings Maintenance page text to reflect that test emails are Veeam only and 1 per button (changed from "3 emails simulating Veeam, Synology, and NAKIVO" to "1 Veeam Backup Job email" per status button)
 
 ### Removed
 - Removed debug logging from ticket linking function after successfully resolving all ticket propagation issues (the logging was temporarily added to troubleshoot why resolved tickets kept appearing on new runs, wrote to AuditLog with event_type "ticket_link_debug" showing ticket_id, code, resolved_at status for every run import, debug code preserved in backupchecks-system.md documentation for future use if similar issues arise)