Repository navigation
Morning Check Schedules Developer Guide
GH #383, asked for by @nebev Β· 5.8.0 Β· user guide: Morning Checks β Schedules
A morning check used to be due every day. Now each check has a Repeats setting: every day, every weekday, weekly on chosen days, or monthly (on a date, the first or last weekday, or the last day). One small PHP class, MorningCheckSchedule, answers "is this check due on this day?". The round, Watchtower and the REST API all ask it, so they cannot disagree. A check that is not due is never hidden: it is greyed out on the round, still recordable, and says when it is next due, when it was last done, or that its last due day was missed.
Decided on the issue (Ed): dropdowns and ticks, no typed cron or Quartz expression; backwards compatible, with no schedule meaning every day; checks not due today greyed out rather than hidden.
| File | What |
|---|---|
π£ includes/morning_check_schedule.php
|
The schedule logic: columns(), isDue(), nextDue(), previousDue(), toArray(). Pure - no database |
π£ includes/services/morning_checks.php
|
saveCheck() takes schedule; scheduleColumns() turns a bad one into a ServiceError
|
π£ api/morning-checks/get_todays_checks.php
|
The round: Due, NextDue, LastDone, MissedOn per check (mcScheduleState()) |
π£ api/morning-checks/add_check.php / update_check.php / get_all_checks.php
|
Forward and return schedule
|
π£ includes/watchtower_queries.php
|
Counts only the checks due today |
π£ api/v1/resources/morning_checks.php + api/v1/spec.json
|
schedule on every check; due on the board |
π‘ morning-checks/schedule.js
|
MCSchedule: the wording (summary, dateText) and the Settings form (init, sync, fill, read) |
π‘ morning-checks/index.php
|
The greyed row, the line under the buttons, Not due in the PDF |
π‘ morning-checks/settings/index.php
|
mcScheduleFields($p) prints Repeats in both the Add and Edit windows |
π΅ morning-checks/style.css (v=7) |
tr.mc-not-due, .mc-due-note, .mc-missed
|
ποΈ morningChecks_Checks
|
Four new columns, below |
π§ͺ tests/morning-check-schedule.php
|
32 date cases; runs in CI (Web exposure job) |
-- database/freeitsm.sql and includes/db_verify_schema.php (Database Verification adds them)
`ScheduleType` VARCHAR(12) NULL, -- NULL = every day | weekdays | weekly | monthly
`ScheduleDays` VARCHAR(20) NULL, -- weekly: ISO days, "1,4" = Monday and Thursday
`ScheduleMonthWhen` VARCHAR(16) NULL, -- monthly: day | first_weekday | last_weekday | last_day
`ScheduleMonthDay` TINYINT NULL, -- monthly 'day': 1-31Every existing check has ScheduleType NULL, so it stays every day - no migration, no data change. Every day is stored as NULL rather than 'daily', so there is one way to say it. Results are untouched: morningChecks_Results still holds one row per check per day, and a weekly check simply has fewer of them.
Plain columns rather than a rule row like task_recurrences: a task repeat answers "when is the next copy made?" and keeps a lot of state; a check only needs "is it due on this day?", which four columns answer with no state at all.
// includes/morning_check_schedule.php
public static function isDue(array $row, string $ymd): bool
{
$type = $row['ScheduleType'] ?? null;
$d = DateTimeImmutable::createFromFormat('!Y-m-d', $ymd);
if (!$d) return true;
$dow = (int)$d->format('N'); // 1 = Monday
switch ($type) {
case 'weekdays': return $dow <= 5;
case 'weekly': $days = self::days($row); return !$days || in_array($dow, $days, true);
case 'monthly': $on = self::monthDate($row, $d); return $on === null || $on === $d->format('Y-m-d');
default: return true;
}
}-
A schedule can never hide a check by accident. An unknown type, a weekly row with no days, a monthly row with no day, or a bad date are all due.
columns()refuses those on the way in (with a message for the person), andisDue()forgives them on the way out. -
The 29th-31st in a shorter month is the month's last day:
min($n, days in month). A check set to the 31st runs on 30 Nov, 31 Dec and 28 Feb. - First / last weekday walks from the 1st forwards, or from the last day backwards, past Saturday and Sunday. Bank holidays are not known; that is said in the help.
-
nextDue()/previousDue()step a day at a time for up to 62 days - enough for any monthly schedule.
// MorningChecksService::saveCheck() - absent = keep what is stored, null = every day
...array_values(array_key_exists('schedule', $in) ? self::scheduleColumns($in['schedule']) : [
$current['ScheduleType'] ?? null, $current['ScheduleDays'] ?? null,
$current['ScheduleMonthWhen'] ?? null, $current['ScheduleMonthDay'] ?? null,
]),Absent means unchanged, as for every other field here: update_check.php is also used by reordering, which sends no schedule, and an older REST client that knows nothing of schedules must not wipe one. columns() tidies weekly days ([4, 1, 1] β "1,4") and throws InvalidArgumentException, which scheduleColumns() turns into a ServiceError('validation', ...) - so the settings page and the API show the same message, e.g. A weekly check needs at least one day.
get_todays_checks.php adds, per check:
| Field | |
|---|---|
Schedule |
{ type, days, month_when, month_day } |
Due |
is it due on the day being viewed? |
NextDue |
not due: the next day it is |
LastDone |
the latest result on or before the day viewed (scheduled checks) |
MissedOn |
not due, and its previous due day went by with nothing recorded on or after it |
One extra query, only for checks that have a schedule: their results over the 62 days before the day viewed.
$prev = MorningCheckSchedule::previousDue($r, $date);
$missed = ($prev !== null && !(isset($lastDone[$id]) && $lastDone[$id] >= $prev)) ? $prev : null;On or after, not on: a weekly Monday check done on Tuesday is not "missed" on Wednesday - it was done, a day late. That is the point of letting a not-due check be recorded.
The row (morning-checks/index.php):
const schedText = MCSchedule.summary(check.Schedule);
if (check.Due === false) {
// "Not due Β· Weekly: Mon, Thu Β· next due Thu 19 Nov Β· Missed Mon 16 Nov" (or "Β· last done Mon 16 Nov")
} else if (schedText) {
// "Weekly: Mon, Thu" - a due check on a schedule still says what its schedule is
}
<tr class="status-${slug}${check.Due === false ? ' mc-not-due' : ''}">The line sits under the status buttons, not under the name, because the PDF reads the name from the first cell's text; the PDF prints Not due instead of Not set for a not-due row with nothing recorded. The chart is unchanged - it only ever counted results that exist.
// includes/watchtower_queries.php - the headline counted every active check
foreach ($mcTotalStmt->fetchAll(PDO::FETCH_ASSOC) as $mcRow) {
if (MorningCheckSchedule::isDue($mcRow, $today)) $mcDueIds[] = (int)$mcRow['CheckID'];
}
$mcTotal = count($mcDueIds);
$mcDueSql = $mcDueIds ? ' AND c.CheckID IN (' . implode(',', $mcDueIds) . ')' : ' AND 1 = 0'; // ints only$mcDueSql goes into the done count and the per-status breakdown too, so a not-due check recorded today cannot make done exceed total. Without this a weekly check reads as outstanding six days in seven - the exact complaint on the issue ("oh - I thought it was already done for the week").
- Every check carries
"schedule": { "type": "weekly", "days": [1, 4], "month_when": null, "month_day": null }. -
POST/PATCH /morning-checks/checksacceptschedule; absent = unchanged (PATCH) or every day (POST);null= every day. A bad one is a422with the same message as the screen. -
GET /morning-checks/boardaddsdueto each check. Not-due checks are still listed - a probe may still record one.
mcScheduleFields('add' | 'edit') prints Repeats (a dropdown), the day ticks (built by MCSchedule.init() with fmtNaiveWeekday, so in the person's language), and for monthly a second dropdown plus the day 1-31. MCSchedule.read() returns null - and the save stops - when a weekly check has no day ticked; the server says the same if anything else gets through.
- TRAP:
display: flexbeats thehiddenattribute..mc-sched-days/.mc-sched-monthare flex, sohiddendid nothing and the month dropdown showed on a weekly check. Fixed with.mc-sched [hidden] { display: none; }. The first headless test read thehiddenproperty, which was right, and missed it - the screenshot caught it. Test what is on screen. - TRAP: Morning Checks'
style.cssstyles every<nav>on its pages (nav:not(.app-sidebar):not(.header-nav) { display: flex }). It made the Settings-on-one-page index (#399) show in Tabs view here. The index is now a<div role="navigation">, and the One page layout targets a class the script adds (sv-host) instead of assuming.container- Morning Checks uses.settings-container. All 22 settings pages with the switch were re-checked in both views. - TRAP: never decide "due" anywhere else. A second copy of the rule in SQL or JavaScript is how the round and Watchtower would start to disagree.
On the test install, through the real endpoints: a weekly Monday check is due Monday and not Tuesday, next due the following Monday, missed on Tuesday until Monday is recorded, then last done Monday; a monthly last-weekday check is due on Mon 30 Nov and not the 19th; a weekly check with no day is refused with its reason; an update that does not mention the schedule keeps it; an existing check is every day; Watchtower's total on a Friday leaves out checks not due. On screen: Repeats in Add and Edit, the list's Weekly: Mon, Thu, the round greyed with Not due Β· Weekly: Mon, Thu Β· next due Thu 19 Nov Β· Missed Mon 16 Nov. Temporary ZZ checks removed.
FreeITSM β an open-source IT Service Management platform Β· github.com/edmozley/freeitsm Β· MIT licence
- Installation
- β° Scheduled tasks (cron jobs)
-
Architecture
- β³ π§Ή Root folder tidy (URL routing)
- β³ π Database Integrity (FKs & constraints)
- β³ π οΈ Database Verification β Developer Guide
- β³ π§© Service Layer (UI + API share code)
- β³ πͺ€ Code traps (the TRAP: comments)
- β³ π Commenting for the Engineering wiki
- β³ π οΈ Engineering wiki scanner - Developer Guide
- β³ π Service-Layer progress
- π€ Contributing (read before a pull request)
- π§ͺ Developer tests
- π PDF exports moved to PDFKit (#254)
- AI Providers
- Internationalisation (i18n)
- Timezones & Time Handling
- π Date & Time Formats
- π± Currencies
- π§ The sidebar (optional module rail)
- π§© Preference templates
- π Display order (modules, Watchtower cards) β Developer Guide
- Theming & Dark Mode
- ποΈ Recent β getting back to what you were doing
- β¨οΈ Command palette (βK)
- π Searching inside tickets
- π Attached documents
-
MobileβFriendly
- β³ π« Mobile: Tickets
- β³ π» Mobile: Assets
- β³ π Mobile: Calendar
- β³ π Mobile: Knowledge
- β³ π¦ Mobile: Service Status
- β³ πΌ Mobile: Watchtower
- β³ π§© Mobile: Problem Management
- β³ π Mobile: Change Management
- β³ πΏ Mobile: Software
- β³ β Mobile: Tasks
- β³ π Mobile: Forms
- β³ π Mobile: Contracts
- β³ π Mobile: Domains
- β³ π Mobile: People
- β³ π Mobile: Projects
- β³ ποΈ Mobile: Files
- β³ π Mobile: LMS
- β³ πΊοΈ Mobile: CMDB
- β³ πΊοΈ Mobile: Network Mapper
- β³ π§ Mobile: Process Mapper
- β³ βοΈ Mobile: Workflow
- β³ π₯οΈ Mobile: System
- β³ π Mobile: Reporting
- β³ π Mobile: System Wiki
- β³ π Mobile: Self-Service Portal
- β³ π§° Mobile: Techniques & Tricks
-
Security
- Layer 1 β which modules you can enter
- β³ π§© Module Access Control
- β³ π οΈ Module Access β Developer Guide
- β³ π Switching modules off
- β³ π οΈ Module availability β Developer Guide
- β³ π Module availability β design (#217)
- Layer 2 β what you can administer
- β³ π Roles & Permissions
- β³ π οΈ Roles β Developer Guide
- β³ π€ Why capabilities are constants
- Layer 3 β the System module
- β³ π Admin Access Control
- Hardening
- β³ π Security review response 2026-08
- β³ π‘οΈ Security hardening 2026-08
- β³ π οΈ Security hardening 2026-08 β Developer Guide
- β³ π‘οΈ Round three β plain English
- β³ π οΈ Round three β Developer Guide
- β³ π‘οΈ CSRF protection (S4) β Developer Guide
- Single Sign-On (SSO)
- ποΈ LDAP & Active Directory
-
π¦ Microsoft Entra ID
- β³ π₯ Importing people and groups
- β³ π» Intune: assets to their primary user
- β³ π’ Organisation chart
- β³ π οΈ Entra directory sync β Developer Guide
- β³ π οΈ Entra import - review (#235)
- β³ π οΈ Entra follow-ups - review (#237-#240)
- β³ π οΈ Intune primary user - review (#236)
- β³ π οΈ Intune after an Entra import - review (#334)
- β³ π οΈ Intune primary user history - review (#338)
- β³ π οΈ Intune asset types - review (#339)
- β³ π οΈ Intune scheduled syncs - review (#344)
- β³ π οΈ Microsoft 365 in Integrations - review (#352)
- β³ π οΈ Organisation chart - reviews (#242, #265)
- π CardDAV contact sync
- Browser Extension
- API Reference
-
π REST API β how it works
- β³ π Script library (PowerShell + Python)
- β³ π Proposal: custom fields, inventory import and change evidence (#194)
- β³ π οΈ Custom fields, evidence + inventory - review (#195-#197)
- β³ π οΈ Long forms in a task's Work view - review (#198)
- β³ π οΈ Empty Procedures fold - review (#247)
- β³ π« REST API: Tickets
- β³ π» REST API: Assets
- β³ π΄ REST API: Problems
- β³ π REST API: Changes
- β³ π REST API: Knowledge
- β³ β REST API: Tasks
- β³ ποΈ REST API: CMDB
- β³ π REST API: Contracts
- β³ ποΈ REST API: Calendar
- β³ πΏ REST API: Software
- β³ π REST API: Domains
- β³ π¦ REST API: Service Status
- β³ βοΈ REST API: Morning Checks
- β³ π REST API: Forms
- β³ βοΈ REST API: Workflow
- β³ π·οΈ REST API: Cost centres
- β³ π’ REST API: Companies
- β³ π REST API: Chart of accounts
- β³ π REST API: Projects
- β³ π‘οΈ API threat protection
- β³ π§βπΌ REST API: Analysts
- β³ πΊοΈ REST API: Network Mapper
- β³ π§ Using the API docs page
- β³ π OpenAPI specification
- β³ β OpenAPI: kept correct
- β³ π οΈ Maintaining the catalogue
- Watchtower
-
Tickets
- β³ Reply subject and replying to one message
- β³ π Live updates
- β³ π οΈ Watching a ticket - Developer Guide (1 of 2)
- β³ βοΈ Ticket address suggestions - Developer Guide
- β³ π οΈ CSAT delay and reminder - Developer Guide
- β³ π οΈ Ticket checklist step types - Developer Guide (1 of 2)
- β³ π οΈ Right-click Attach checklist - Developer Guide
- β³ π οΈ Checklists in the REST API - Developer Guide
- β³ π A ticket's related block and attachments - Developer Guide
- β³ π οΈ Inbox.js map β Developer Guide
- β³ π οΈ Floating windows & the file viewer β Developer Guide
- β³ π οΈ Tickets settings β Developer Guide
- β³ π Simpler ticket and task forms - design (#218)
- β³ ποΈ The ticket workspace
- β³ π Forms on tickets
- β³ π The ticket table
- β³ π Rota copy and paste β Developer Deep Dive
- β³ β Checklists & SOPs
- β³ βοΈ Mandatory fields
- β³ π§Ύ Custom ticket fields
- β³ π·οΈ Ticket categories
- β³ π§Ύ A type for every new ticket
- β³ π₯ Assigning tickets to a team, and escalation
- β³ π’ One board across every company
- β³ π Many companies: searchable lists (#358)
- β³ π Ticket dashboard β Developer Guide
- β³ Mailbox Authentication
- β³ π€ Email send log
- β³ βοΈ Emailed reports
- β³ π Attachment size limits and large emails
-
β³ Basic IMAP mailboxes
- β³ π Basic IMAP without the PHP extension (#257)
- β³ π οΈ Basic IMAP client β Developer Guide
- β³ π§ͺ Basic IMAP client β Testing and verifying
- β³ π οΈ Basic IMAP - Sent copy - Developer Guide (#270)
- β³ π€ PR #400 Sending through a relay without a login
- β³ π οΈ Verifying a mail folder β Developer Guide
- β³ π οΈ Mailbox providers β Developer Guide
- β³ π οΈ How Gmail mail collection works β Developer Guide
- β³ Email rendering & images
- β³ SLA Management
- β³ WhatsApp channel
-
β³
βοΈ Telegram channel - β³ β CSAT company scope and filters β Developer Guide
- β³ π₯ Microsoft Teams channel
- β³ π¨οΈ Mattermost channel
- β³ π¬ Web chat channel
- β³ π£ Slack channel
- β³ π Linking tickets
- β³ β Record previews
- β³ π Ticket notes: internal or shared
- β³ ποΈ Canned responses
- β³ βοΈ Limiting replies to particular senders
- β³ π¨ Telling the analyst a ticket is theirs
- β³ βοΈ Email signatures
- β³ π The public web address
- β³ π’ Ticket numbering
- β³ π Raising a ticket for someone else
- β³ π Merging tickets
- β³ π Confidential tickets
- β³ π₯ Portal managers
- β³ π Who has seen a ticket
- β³ π Reading long tickets
- β³ β¨ Reply Cleanup prompt and history
- β³ β Splitting tickets
- β³ β Selecting several tickets
- β³ ποΈ The folder pane
- β³ π½ Just my tickets, or no closed ones
- β³ π οΈ Snoozing tickets β Developer Guide
- β³ π₯ Collision detection
- β³ β±οΈ Time tracking
- β³ π Case reports - a ticket and its work as one PDF
- β³ π Scheduled work in your own calendar
- Problem Management
-
Tasks
- β³ π οΈ Task ID and hover card - review (#405)
- β³ π οΈ Task board and subtasks β Developer Guide
- β³ π§βπ€βπ§ People on a task ("Involved")
- β³ π Repeating tasks
- β³ π’ Moving a task between companies
- π Projects
-
Assets
- β³ π οΈ Asset list by type - review (#340)
- β³ π’ Moving an asset between companies
- β³ π Shared asset locations
- β³ π§βπΌ Assigning assets to analysts
- β³ π Warranty and lease alerts
- β³ π Leases
- β³ π Saved table views
- β³ π¨οΈ Recording anything, and importing it
- β³ π§© Asset type layouts
- β³ π Inventory freshness
- β³ π Linked configuration item
- β³ π Connected assets
- β³ π Asset review
- β³ π Missing information
-
β³ π·οΈ QR asset labels
- β³ π οΈ QR asset labels β Developer Guide
- β³ π Asset label designer - design (#229)
- β³ π· Asset scanning β Developer Guide
- β³ π οΈ Asset tag numbering β Developer Guide
- β³ π οΈ Asset reconciliation β Developer Guide
- β³ π οΈ Reconciliation, tags + labels - review (#164)
- β³ π Who holds what, and handover documents
- β³ π₯οΈ The inventory agent (PowerShell)
- β³ ποΈ Proxmox VE servers
- β³ βοΈ VMware Cloud Director servers
- β³ πͺ Hyper-V and Failover Clusters
- β³ π Linking equipment to tickets
- β³ βοΈ Follow-up tasks on a ticket
- Knowledge
- Change Management
- Calendar
- Morning Checks
- Reporting
- Software
-
Forms
- β³ π¨ The form designer β Developer Guide
- β³ π Layout & the grid β Developer Guide
- β³ ποΈ Collections β grouping submissions
- β³ π Submissions as PDFs
- β³ β‘ What happens next β a form's own actions
- β³ π οΈ Sections & conditional logic β Developer Guide
- β³ π οΈ Lookup fields β Developer Guide
- β³ π‘οΈ Catalogue request approvals
- People
- Starters & leavers
- Domains
- ποΈ Files
- Contracts
- Service Status
- π Notifications
- π¨ War Room
-
Self-Service Portal
- β³ π¨ Branding the portal
- β³ π What people can do
- β³ π Help Centre
- β³ πͺ Landing page
- β³ π¨ Login screen designer
- β³ π οΈ Back to your page after sign-in - review (#407)
- β³ π Request catalogue
- β³ π Portal privacy
- β³ π₯ Portal managers
- β³ π Contact details
- β³ π οΈ Developer guide
- LMS
- Process Mapper
-
CMDB
- β³ π§± Designing your CMDB
- β³ π οΈ CMDB β Developer Guide
- β³ π οΈ Impact analysis β Developer Guide
- β³ π οΈ Data quality β Developer Guide
- β³ π οΈ Record references β Developer Guide
- β³ π οΈ CMDB assistant - Developer Guide
- β³ π Linked assets
- β³ π Linking an asset to its CI - design (#201)
- β³ π Discovery and redundancy-aware impact - design (#199)
- β³ π οΈ Relationship wording - review (#297)
- Network Mapper
-
Workflows
- β³ π Branches: If / Otherwise and Choose by value
- β³ π οΈ Workflow engine β Developer Guide
- β³ π οΈ Workflows for tasks β Developer Guide
- β³ π οΈ Workflow notes on a ticket β Developer Guide
- β³ π οΈ Workflow category routing β Developer Guide
- β³ π Workflows in order, child tickets - design (#304)
- β³ β° Time-Based Triggers
- β³ πͺ Webhooks
- β³ π¬ Webhook Message Formats
- β³ π HTTPS Certificates & CA Bundles
- β³ π οΈ SSL Verification β the Global Setting
- β³ π Workflow & Webhook Pitfalls
- Issue trackers (Jira, Azure DevOps)
- π‘ Zabbix (monitoring)
- π¬ Microsoft Teams alerts
- π 3CX (phone system)
-
System
- β³ π οΈ System cards by topic - review (#347)
- β³ π¦ Microsoft 365 (Entra ID and Intune)
- β³ π οΈ Preferences β Developer Guide
- β³ ποΈ Settings on one page
- β³ π§Ή Maintenance
- β³ πΎ Storage usage
- β³ βοΈ Emailed reports
- β³ π Finding people in the Analysts list
- β³ πͺ When an analyst leaves
- β³ π οΈ System β Branding β Developer Guide
- β³ π©Ί Page health (D019) β Developer Guide
- β³ β Feature Bingo
- β³ π Locations
- β³ π·οΈ Cost centres
- β³ π Chart of accounts
- β³ π· Photo Album
- β³ Demo Data
- β³ π οΈ Demo Data β Developer Guide
-
Overview
- β³ π Progress tracker
- β³ Concepts & vocabulary
- β³ Email routing & mailboxes
- β³ Settings: global vs per-company
- β³ Users & self-service
- β³ Staff cross-company access
- β³ One company supporting another
- β³ π’ One board across every company
- β³ Worked examples
- β³ Pitfalls & gotchas
- β³ Scope: what it's for
- β³ π οΈ Developer Guide (make a module multi-company)
- β³ ποΈ Case study: CMDB (a linked graph)
- β³ π§ͺ Test harness (prove it's isolated)
- What this is
-
π Bugs resolved
- β³ π #413 Reading pane too narrow on tablets
- β³ π± #412 Sign-in card cramped on phones
- β³ π§ #411 Header buttons out of reach
- β³ π± #386 Project stuck in an old currency
- β³ π₯οΈ #393 Header ran off the screen
- β³ π±οΈ #395 Ticket flyouts ran off the bottom
- β³ π PR #401 Change editor used hardcoded priorities
- β³ π Knowledge drafts could not be published
- β³ π§© #392 Project dialogs shared element ids
- β³ πΌοΈ #391 Knowledge images from your computer
- β³ π #375 REST API wall-clock times
- β³ π #374 Calendar popup ran off the screen
- β³ π’ #373 All companies: Changes, CMDB, Starters
- β³ π’ #356 Assets People and All companies
- β³ π #366 LMS demo data would not import
- β³ π #362/#365 Team handover showed only a name
- β³ π #365 The bell credited the wrong person
- β³ ποΈ #369 Inbox empty until Database Verification
- β³ πͺ #360 Links opened inside the ticket
- β³ π #354 Workspace Links missed tasks
- β³ π Task company checks in the API (5.5.0)
- β³ π Asset holders through the API (5.4.0)
- β³ π Files folder delete did not check inside (5.4.0)
- β³ π The Intune tab did not check the company
- β³ π #332 Files viewer would not open
- β³ π #333 Note attachments downloaded
- β³ πͺ #326/#327 Form webhook Full record
- β³ π #325 Form PDF download failed
- β³ π Small fixes in 5.1.0
- β³ π CMDB relationships read backwards (5.1.0)
- β³ π #301 CSAT delay was never applied
- β³ π #281 Comments imported from Jira never arrived
- β³ π #288 A change failed to open with Enforce approvals on
- β³ π Long non-Latin articles never got an embedding
- β³ π« #280 Email lookups scanned the whole table
- β³ β #266 Dragging a task told nobody
- β³ π #255 Article previews showed HTML codes
- β³ π #252 A link to a Knowledge article did not open
- β³ π #254 PDFs could not print Polish
- β³ π #250 Clicking a folder left the open article on screen
- β³ π« #260 The dashboard cog did nothing
- β³ π« #248 A department rule never matched on four routes
- β³ π A directory account could be matched to someone else
- β³ π« #244 Reply went to the assigned analyst
- β³ π Mailbox sign-in was not checked
- β³ π Four weaknesses around signing in
- β³ π A lookup answer could name any record
- β³ π« #227 A mailbox could not be deleted
- β³ π« #226 A picture on a note could not be closed
- β³ π» #222 The Assets page never loaded in 4.3.0
- β³ βοΈ #214 A "contains" condition did not match capitals
- β³ βοΈ #216 A workflow email from a chosen mailbox always failed
- β³ π³ The Docker image was missing PHP extensions
- β³ π A failed DNS lookup read as a missing record
- β³ π A link could change data
- β³ π Access outlived its removal
- β³ π Knowledge articles could run scripts
- β³ π Knowledge writes ignored permissions
- β³ π Company boundaries (Oct 2026)
- β³ π Smaller gaps (Oct 2026)
- β³ π Escaped text could leave its attribute
- β³ π Task descriptions were not cleaned
- β³ π Task documents ignored company scope
- β³ π Repeating tasks ignored company scope
- β³ π¬ #183 Mailbox checks overlapped
- β³ π #188 Transfer lock shown off when unknown
- β³ β #184 Subtask names and Overdue
- β³ π§© #186 Teams: the buttons did nothing
- β³ π Text in a change could run script
- β³ π AI settings changed without the AI permission
- β³ πͺ #178 Deleting an analyst failed
- β³ π« A team with no departments showed 0 tickets
- β³ π Projects: adding a phase did nothing on Save
- β³ π Leavers could still sign in
- β³ πΌοΈ Logo and courses broke on Apache with PHP-FPM
- β³ π’ Chat tickets ignored your ticket numbering
- β³ π Dates shown as a dash, or in server time
- β³ π Assets β Users showed people from other companies
- β³ π Restricted analysts could read other modules' data
- β³ πΌοΈ Replies with a picture in the thread failed to send
- β³ π Reply attachments never reached the customer
- β³ π οΈ Outbound email attachments β Developer Guide
- β³ π A global SSO provider was missing from the portal
- β³ π Behind a proxy, the SSO redirect said http
- β³ βοΈ The portal tagline moved when you saved it
- β³ π¨ The portal settings screen forgot what you saved
- β³ π‘οΈ The approvals inbox said "Error" and nothing else
- β³ π A table's answers were missing from the PDF
- β³ β A single-select column let you tick every option
- β³ π The portal ignored a form's field widths
- β³ π The tasks board stopped taking clicks
- β³ ποΈ #121 The index list is out of date after upgrading
- β³ π #133 The calendar subscription was empty
- β³ π #131 Tasks always reopened on the board
- β³ π₯ #129 Every page returned HTTP 500 after upgrading
- β³ π³ #127 A PHP warning above the System page
- β³ π #126 Notes stamped with the server's clock
- β³ π Storing every date in UTC
- β³ πͺ The portal was down for everyone signed in
- β³ βοΈ #120 Workflow notes could never be written
- β³ βοΈ #123 Three errors when running Database Verification
- β³ π #122 The description box was a stub in the corner
- β³ π£ Demo data deleted real accounts
- β³ π #117 Sign-in redirected to the wrong address
- β³ π¨ #108 The priority dot was invisible
- β³ β±οΈ #116 Time logged from the right-click menu
- β³ π #114 API keys refused by our own guard
- β³ ποΈ #110 Assigning a task told nobody
- β³ πͺ #107 Signed out while still working
- β³ π #103 "Share with Requester" reached nobody
- β³ π #102 Search found nothing for hyphens
- β³ πͺ #101 Source code editor opened behind
- β³ βοΈ #88 Subtasks could not be ticked off
- β³ π» #84 Asset deep link selected nothing
- β³ π« #79 A new ticket arrived with no status
- β³ π§ #79 A ticket from email did not say so
- β³ π #78 Bell opened to nothing
- β³ π¬ #77 Mail only collected from Inbox
- β³ π #74 The default password could not be changed
- β³ π¦ #70 Renaming an impact level
- β³ π€ #67 App-only mailboxes could not send
- β³ π #45 Verify only ever worked for Microsoft
- β³ π #45 IMAP reported as not authenticated
- β³ βοΈ An email template stopped escaping itself
- β³ π The portal dashboard showed the wrong time
- β³ π’ The folder said 99 and the list showed 96