"This release focused on improving operational clarity and usability by strengthening dashboard guidance, introducing a solid reporting foundation, and significantly refining the Run Checks review workflow for daily accountability.",
],
"categories":[
{
"category":"Dashboard & User Guidance",
"items":[
{
"title":None,
"details":[
"Added a comprehensive explanatory section to the Dashboard describing how Backupchecks collects, normalizes, and evaluates backup results.",
"Clarified dashboard counters, job statuses, overrides, and operational workflows.",
"Introduced clear guidance emphasizing the goal of keeping the Run Checks page empty or near-empty as proof of daily review and accountability.",
"Positioned Backupchecks explicitly as a monitoring and validation layer that complements existing backup software.",
],
}
],
},
{
"category":"Navigation & Usability",
"items":[
{
"title":None,
"details":[
"Implemented automatic redirection to the Dashboard on a user’s first visit of each day, improving daily visibility of system status.",
"Refactored the Settings area into clearly separated sections (General, Imports, Users, etc.) for better usability and structure.",
],
}
],
},
{
"category":"Dashboard News",
"items":[
{
"title":None,
"details":[
"Added a per-user Dashboard News section with read/unread tracking.",
"Enabled full admin management of news items (create, edit, delete, pin, severity, publish window).",
"Provided admin insight into read statistics and the ability to reset read status.",
],
}
],
},
{
"category":"Reporting – Foundation",
"items":[
{
"title":None,
"details":[
"Introduced the initial reporting framework focused on raw, immutable data for auditability.",
"Added object-based reporting across multiple jobs with aggregated success, warning, failed, missed, and override metrics.",
"Prepared the data model for CSV export, future PDF generation, scheduling, and email delivery.",
"Enabled reporting access for admin, operator, and reporter roles in phase 1.",
],
}
],
},
{
"category":"Reports UI & Generation",
"items":[
{
"title":None,
"details":[
"Added an initial Reports UI to define, generate, and manage reports.",
"Enabled raw data preview directly in the UI with pagination support.",
"Implemented backend endpoints to generate and retrieve report data on demand.",
"Replaced the “New report” modal with a dedicated Create Report page.",
"Added month-based date selection, quick-select options, and multi-customer reporting support.",
"Enabled actual report generation while keeping scheduling as a non-functional placeholder.",
This release focused on improving operational clarity and usability by strengthening dashboard guidance, introducing a solid reporting foundation, and significantly refining the Run Checks review workflow for daily accountability.
### Dashboard & User Guidance
- Added a comprehensive explanatory section to the Dashboard describing how Backupchecks collects, normalizes, and evaluates backup results.
- Clarified dashboard counters, job statuses, overrides, and operational workflows.
- Introduced clear guidance emphasizing the goal of keeping the Run Checks page empty or near-empty as proof of daily review and accountability.
- Positioned Backupchecks explicitly as a monitoring and validation layer that complements existing backup software.
### Navigation & Usability
- Implemented automatic redirection to the Dashboard on a user’s first visit of each day, improving daily visibility of system status.
- Refactored the Settings area into clearly separated sections (General, Imports, Users, etc.) for better usability and structure.
### Dashboard News
- Added a per-user Dashboard News section with read/unread tracking.
- Enabled full admin management of news items (create, edit, delete, pin, severity, publish window).
- Provided admin insight into read statistics and the ability to reset read status.
### Reporting – Foundation
- Introduced the initial reporting framework focused on raw, immutable data for auditability.
- Added object-based reporting across multiple jobs with aggregated success, warning, failed, missed, and override metrics.
- Prepared the data model for CSV export, future PDF generation, scheduling, and email delivery.
- Enabled reporting access for admin, operator, and reporter roles in phase 1.
### Reports UI & Generation
- Added an initial Reports UI to define, generate, and manage reports.
- Enabled raw data preview directly in the UI with pagination support.
- Implemented backend endpoints to generate and retrieve report data on demand.
- Replaced the “New report” modal with a dedicated Create Report page.
- Added month-based date selection, quick-select options, and multi-customer reporting support.
- Enabled actual report generation while keeping scheduling as a non-functional placeholder.
### Run Checks – Multi-Select Improvements
- Added Shift-click multi-selection for efficient bulk review.
- Iteratively fixed edge cases including:
- Off-by-one range selection issues
- Checkbox and row highlight desynchronization
- Last-row selection bugs
- Browser text selection interference
- Improved “Select all” checkbox behavior:
- Clearing selection when indeterminate
- Correctly resetting from the indeterminate state
- Ensuring consistent mouse and keyboard interaction
### Overall Result
- Improved clarity, accountability, and daily workflow guidance across the application.
- Established a solid, extensible reporting foundation.
- Significantly enhanced usability and reliability of the Run Checks review process.
- Added a comprehensive explanatory section to the Dashboard, positioned directly below the legend.
- Introduced detailed documentation describing how Backupchecks collects, normalizes, and evaluates backup results across multiple backup solutions.
- Clarified the purpose and behavior of dashboard counters, job statuses, and override indicators.
- Expanded the explanation of the Daily Jobs and Run Checks workflows, including the review, follow-up, resolution, and override processes.
- Documented the operational goal of maintaining an empty or near-empty Run Checks page to ensure full review and accountability.
- Clearly positioned Backupchecks as a monitoring, validation, and control platform that enhances, but does not replace, existing backup software.
---
## v20251231-02-daily-first-open-dashboard
- Added logic to automatically redirect users to the Dashboard on their first website visit of each day.
- The redirect is applied per browser session after authentication, ensuring normal navigation afterwards.
- Excluded API endpoints and static asset requests from the redirect to prevent unintended side effects.
- Ensured the behavior is transparent to users while improving daily visibility of overall system status.
---
## v20251231-03-dashboard-news-settings-sections
- Added a Dashboard News section displaying active announcements per user.
- Implemented per-user read tracking, allowing users to mark news items as read so they disappear only for that user.
- Added admin management for News items in Settings (create, edit, delete, pin, severity, active state, publish window).
- Added admin visibility into read status per news item, including read counts and user timestamps.
- Implemented admin action to reset read status for a news item.
- Refactored the Settings page into separate sections to improve usability and prevent overly long pages.
---
## v20251231-04-settings-tabs-restructure
### Settings
- Removed the collapse-based layout from **Settings → General** and converted it to a fixed section view for improved clarity.
- Moved **Import configuration** from **Settings → General** to the dedicated **Imports** section.
- Moved **User Management** from **Settings → Maintenance** to the dedicated **Users** section.
- Moved **Manual mail import** from **Settings → Maintenance** to the **Imports** section.
- Simplified and clarified the overall Settings structure by grouping related functionality into dedicated sections.
---
## v20251231-05-reporting-raw-data-foundation
### Reporting – Foundation
- Introduced the initial reporting foundation focused on raw data collection.
- Added support for object-based reporting across multiple jobs.
- Implemented immutable report snapshot data to ensure auditability.
- Added aggregated summary data to calculate success, warning, failed, missed, and override metrics per object.
- Prepared reporting structures to support CSV output and future PDF generation.
- Enabled both one-time and scheduled report concepts at the data and API level.
- Ensured report data is reusable for downloads and email delivery.
- Aligned reporting permissions so admin, operator, and reporter roles have equal access in phase 1.
- Designed the reporting model to be extensible for future RBAC, UI, and visualization enhancements.
---
## v20251231-06-reports-ui-placeholders
- Added an initial Reports UI to create, view, and manage report definitions for testing purposes.
- Implemented UI components to generate and download raw report data as CSV.
- Fixed the Run Checks header “select all” checkbox behavior: when the checkbox is in an indeterminate (partial selection) state, clicking it now clears all selected rows instead of selecting all rows.
- Prevented unintended full selection when toggling from an indeterminate state.
- Ensured consistent behavior between mouse click and keyboard (Space) interaction on the header checkbox.
- Fixed the Run Checks header “select all” checkbox: when it is indeterminate (partial selection), clicking it now clears the current selection instead of selecting all rows.
- Implemented click interception before the browser toggles the checkbox state to prevent unintended full selection from the indeterminate state.
- Added consistent keyboard behavior: pressing Space on the indeterminate header checkbox now also clears the selection.
- Fixed an issue on the Run Checks page where the “Select all” checkbox could remain visually stuck in the indeterminate (`-`) state after clearing the current selection.
- Ensured the header checkbox state is re-synced after the click/change cycle so it correctly reflects the row selection state.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.