ivooskamp/backupchecks
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

v20260101-03-run-checks-page-guide-text #1

Merged
ivooskamp merged 2 commits from v20260101-03-run-checks-page-guide-text into main 2026-01-03 15:02:52 +01:00
Conversation 0 Commits 2 Files Changed 4 +11
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 9f42b8163e - Show all commits

11
docs/changelog.md
View File

@ -105,6 +105,17 @@
- Updated report generation logic to handle single-customer, multi-customer, and all-customer scopes. - Updated report generation logic to handle single-customer, multi-customer, and all-customer scopes.
- Prepared reporting output for use cases such as account management and operations-wide overviews. - Prepared reporting output for use cases such as account management and operations-wide overviews.
---
## v20260101-03-run-checks-page-guide-text
- Added a workflow guide to the Run Checks page explaining its purpose in daily operational triage.
- Emphasized that the main objective is to keep the Run Checks page as empty as possible.
- Clarified that every run must be marked as reviewed to demonstrate that backups are actively checked.
- Explicitly stated that after adding a ticket number or remark, the run must still be marked as reviewed.
- Explained the role of the resolved status within the Run Checks workflow.
- Placed the guide directly on the Run Checks page (no popup), aligned with the dashboard explanation style.
================================================================================================================================================ ================================================================================================================================================
## v0.1.14 ## v0.1.14