Skip to content

RivetIT 26.10.80

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 01 Nov 06:53
· 349 commits to production since this release
  • Administration > Update: the check for generated vendor/composer files that differ from the repository is now a Note, not a warning (those files are regenerated by composer install). The RMM data store tile shows the short PostgreSQL version; the full version string is on hover.

  • Project tasks, phase 1: priority, description, labels, colour, and a task detail pop-up (database 2.6.207). Every project task can now carry a priority (none, low, medium, high, urgent), a description, labels (global ones, or ones that belong to one project) and a card colour. The Kanban card shows the priority as a coloured left edge plus a badge with its name (never colour alone), the labels as chips, an icon when there is a description, an Overdue due date, a progress bar and the assignee, and is more compact so more cards fit on a phone. The board has a Sort (manual order or priority) and filters by priority, label and assignee; these only change what you see, never the saved order. Click a card title or the expand icon for the task detail pop-up with every field editable; New Task and Edit Task have the new fields too, and the project's task list shows the priority marker and label chips.

  • Task actions: Delete (asks first; needs the same Service Desk level as before, removes the task's labels links), Duplicate (copies fields and labels, not completion) and Move to another project are in the detail pop-up, and a small per-card menu (Edit, Create ticket, Mark complete, Duplicate, Delete). The old Delete link in the task list now also applies the client-access check to project-only tasks (it only checked ticket tasks before).

  • Kanban drag fix. The hamburger drag handle (which overlapped the ticket and edit icons on phones) is gone. Grab a card anywhere to drag it: with a mouse it drags at once; on a touch screen press and hold for about a quarter of a second, then drag, so a quick swipe still scrolls the board. Moving cards between lanes and the saved order work exactly as before.

  • API: GET/POST /tasks, GET/PATCH/PUT/DELETE /tasks/{id} (new; scopes api:tasks:read / write / delete, role level 1 / 2 / 3, department scope), and priority, priority_name, description, color, labels on every task (including in GET /projects/{id}). Existing fields and clients are unchanged. See docs/API.md and api/v1/openapi.yaml.
    Deploy notes: take a database dump first, then Update Database (Administration > Update, or php scripts/update_cli.php --update_db). One additive, idempotent step (2.6.206 -> 2.6.207): tasks.task_priority (default 0), tasks.task_description, tasks.task_color, and the new task_labels / task_label_links tables. Nothing is back-filled. New code on a database that has not been updated yet keeps working (the new fields simply do not show).

  • Project tasks, phase 2: checklists, subtasks and comments (database 2.6.208). The task pop-up has a Checklist (add, tick, edit, delete, move up / down; the card shows 3/5), Subtasks (add, tick to complete, make a regular task again; the card shows 2/3; a subtask is a full task in the same project, one level deep, and shows in its parent's pop-up rather than as a card of its own) and Comments (add, edit your own, delete your own; administrators can delete any; shows author and time; the card shows a count). These save as you click, without leaving the pop-up. Deleting a task deletes its checklist and comments but never its subtasks: they stay in the project as ordinary tasks. Duplicate copies the checklist (unticked) and the subtasks. Moving a parent moves its subtasks; a subtask cannot be moved on its own.

  • Project tasks, phase 3: several assignees, files, reminders, repeating tasks (database 2.6.209). Several people can be on a task (the "Assigned To" person stays the primary, so older screens and apps keep working; the card shows avatars and the assignee filter matches anyone on the task; existing assignees are carried over). Files can be attached in the pop-up (scripts, web pages and installers are refused; downloads need the same department access as the task and are always sent as a download). A task can have a reminder (a date and time, or relative to the due date); the cron job (cron/task_reminders.php, run by the main cron) sends an in-app / push notification to everyone on the task once (administrators when nobody is assigned; no email). A task can repeat every N days / weeks / months / years: completing it (drag to Done, Mark complete, the pop-up, the API) creates the next occurrence once, with the due and start dates moved on (a task finished late gets a due date of today or later, month ends are clamped, not skipped), checklist unticked, same people, labels and reminder offset; comments and files are not copied.

  • API: every task gains parent_id, assignees, checklist, subtasks, comment_count, attachment_count, reminder_at, reminder_sent_at, repeat; parent_id, assignee_ids, reminder_at, repeat are writable; new sub-resources /tasks/{id}/checklist, /subtasks, /comments, /attachments. Existing fields and clients are unchanged. See docs/API.md and api/v1/openapi.yaml.
    Deploy notes (phases 2 and 3): take a database dump first, then Update Database. Two additive, idempotent steps: 2.6.208 (tasks.task_parent_id, task_checklist_items, task_comments) and 2.6.209 (tasks.task_reminder_at / task_reminder_sent_at / task_repeat_interval / task_repeat_unit / task_repeat_spawned_at, task_assignees with a one-time back-fill from tasks.task_assigned_to, task_attachments). Attachments are stored in uploads/task_attachments/ (created on first upload; the web server user must be able to write to uploads/; this folder is under /uploads/, so keep the nginx rule that stops scripts running there). New code on a database that has not been updated yet keeps working (the new panels and fields simply do not show).

  • RivetCore parity pass (Core 1.0.0-rc.55; database 2.6.210). Everything RivetCore's edition prompts ask for that RivetIT did not have yet. Nothing is switched on by this change.

    • Compliance frameworks (RivetCore #92 phase 4). New page Administration > Compliance framework: select a built-in or custom framework, copy one, edit it (every save is a new version, a stale edit is refused, restore any older version), archive, delete (only a never-selected one), export and import (JSON, 64 KiB, hostile files change nothing), and record a restore test. Once a framework is selected its requirements (backup age, off-site copy, encryption, restore-test age, retention minimums, log presets) are checked on the Compliance status page and recorded in snapshots, its retention minimums are refused below in the RMM settings and raised in the audit-trail cleanup, and every change is audited. With no framework selected nothing differs from before.
    • Backup facts. Each backup run now records which stores it really contained, whether it was encrypted and how long its writer keeps sets (backup_runs.run_stores, run_encrypted, run_retention_days; filled by the in-app backup and by deploy/backup.sh). The compliance checks judge those facts and the backup file's header, not configuration. The in-app backup now includes the RMM PostgreSQL store (rmm-postgres.dump, through RivetCore's BackupHook, password through a 0600 PGPASSFILE only) when that store is in use; a dump that is expected and fails fails the whole run (no zip is written, the run is recorded as failed).
    • Reporting / Power BI (RivetCore #91 phase 4). New page Administration > Reporting / Power BI and RivetIT's own views rpt_clients, rpt_sites, rpt_assets, rpt_tickets, rpt_alert_tickets, rpt_sla (allow-listed columns, no free text, client_id on every row, frozen by a fixture). Create, rotate and drop a dedicated read-only database account (MariaDB/MySQL, and a PostgreSQL role when the RMM store is PostgreSQL) with a generated password shown once and an administrator login that is used once and never kept; test the connection as that account; copy Power Query for this install; computed warnings. Timestamps in the RivetIT views are converted to UTC from the company time zone by zone name (daylight saving time proven on MariaDB 10.11); on a server without time zone tables the views are created unconverted and the page says so.
    • Security baseline. docs/security/EDITION_BASELINE.json states honestly, per RivetCore control, what RivetIT enforces (3 enforced, 15 partial, 2 gap), checked by scripts/edition-baseline-check.php (new CI job security baseline). New Security and trust page, public at /trust.php and an administrator copy with per-control detail; it uses only RivetCore's approved wording and a test fails the build if it ever says "SOC 2 compliant" and the like. The staff password minimum can no longer be set or stored below RivetCore's floor of 12.
    • RMM. An asset that moves department (asset edit, inline edit) now takes its RMM device with it through DeviceService::transfer(): jobs, open alerts and the stored log/change history follow, and a PostgreSQL store that is down repeats the history move later. The device-type rule of EndpointAssets::createForDevice now applies RivetCore's pre-rc.29 OS rule when a caller sends no type (the Core conformance kit pins it).
    • Tests. Three stale conformance tests repaired (API keys became integration clients, https-only webhooks, the asset types RivetIT really has); new tests for backup facts (Core kit plus the edition rules), the in-app PostgreSQL backup, frameworks, reporting views/page/PostgreSQL role, the trust page and the baseline check.
      Deploy notes: take a database dump first, then run the database update (Administration > Update, or php scripts/update_cli.php --update_db). One additive, idempotent step (2.6.209 -> 2.6.210): three nullable columns on backup_runs and the six rpt_ views. The reporting account is NOT created by the update. If the database server's time zone tables are not loaded (mariadb-tzinfo-to-sql), the RivetIT reporting views are created without UTC conversion; load them and press "Rebuild the RivetIT views".