Repository navigation
Asset Missing Information Developer Guide
GH #404 Β· 5.8.0 Β· user page: Missing information Β· design background: Asset type profiles decision 2 ("any later completeness check refers to the built-in field itself and flags rather than refuses")
Two small tables and one service. A type's expected fields are rows; a per-asset Not applicable is a row. The list of what is missing is not stored - it is a query over the assets as they are now. That one choice gives the issue's hardest requirement for free: "filling a field removes its finding; clearing it makes it outstanding again ... from the UI, imports and API". No write route had to change, because none of them is asked to keep anything up to date.
| File | What |
|---|---|
π£ includes/services/asset_completeness.php
|
AssetCompleteness: the built-in field list, expectations, the findings query, Not applicable |
π£ api/assets/missing_info.php
|
GET the list / one asset; POST Not applicable on or off |
π£ api/assets/save_asset_type.php, api/assets/get_asset_types.php
|
carry expected (and expected_custom) with a type, like layout
|
π£ asset-management/missing/index.php
|
the Missing information page |
π£ asset-management/includes/header.php
|
the header button, only once something is expected |
π£ asset-management/index.php
|
the Key info line, loadMissingNotice()
|
π£ asset-management/settings/index.php
|
the type dialog's Expected information block, expSetup() / expCollect()
|
π£ includes/services/asset_merge.php
|
Not applicable follows a merge |
ποΈ database/freeitsm.sql, includes/db_verify_schema.php, api/system/db_verify.php, includes/db_verify_indexes.php (generated) |
the two tables, their foreign keys and unique keys |
π£ includes/analyst_lifecycle.php
|
set_by_analyst_id is history |
π§ͺ tests/asset-missing-info.php
|
28 checks |
CREATE TABLE IF NOT EXISTS `asset_type_expected_fields` (
`id` INT NOT NULL AUTO_INCREMENT,
`asset_type_id` INT NOT NULL,
`field_key` VARCHAR(40) NOT NULL, -- 'purchase_date', 'supplier_id', ... or 'custom:<asset_fields.id>'
PRIMARY KEY (`id`),
UNIQUE KEY `uq_asset_type_expected` (`asset_type_id`, `field_key`),
CONSTRAINT `fk_ate_type` FOREIGN KEY (`asset_type_id`) REFERENCES `asset_types` (`id`) ON DELETE CASCADE
);
CREATE TABLE IF NOT EXISTS `asset_field_not_applicable` (
`id` INT NOT NULL AUTO_INCREMENT,
`asset_id` INT NOT NULL,
`field_key` VARCHAR(40) NOT NULL,
`set_by_analyst_id` INT NULL, -- lifecycle: history
`set_datetime` DATETIME NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `uq_asset_field_na` (`asset_id`, `field_key`),
CONSTRAINT `fk_afna_asset` FOREIGN KEY (`asset_id`) REFERENCES `assets` (`id`) ON DELETE CASCADE
);No row means nothing expected - so an install that never ticks a box behaves exactly as before, and the header button never appears (acceptance criterion 1). field_key is a string rather than a column per field so a custom field and a built-in one are the same kind of thing.
public const BUILTIN = [
'asset_tag' => ['identity', 'asset_tag', 'text'],
'service_tag' => ['identity', 'service_tag', 'text'],
'location_id' => ['identity', 'location_id', 'ref'],
'manufacturer' => ['make_model', 'manufacturer', 'text'],
'model' => ['make_model', 'model', 'text'],
'purchase_date' => ['financial', 'purchase_date', 'value'],
'purchase_cost' => ['financial', 'purchase_cost', 'value'],
'supplier_id' => ['financial', 'supplier_id', 'ref'],
'cost_centre_id' => ['financial', 'cost_centre_id', 'ref'],
'order_number' => ['financial', 'order_number', 'text'],
'warranty_expiry' => ['financial', 'warranty_expiry', 'value'],
];[section, column, kind]. The kind decides what "missing" means - criterion 3 of the issue:
| kind | Missing when | So |
|---|---|---|
text |
NULL or TRIM(col) = ''
|
spaces-only is missing |
ref |
NULL or 0
|
an unselected reference |
value |
NULL only |
a cost of 0 is filled in |
The hardware and operating-system fields are deliberately not offered: the agent writes them, and a person cannot usefully "fill in" a CPU. Adding a field later is one line here, one label string, nothing else.
missingSql() turns one key into a SQL test on alias a:
private static function missingSql(string $key): array
{
if (isset(self::BUILTIN[$key])) {
[, $col, $kind] = self::BUILTIN[$key];
if ($kind === 'text') return ["(a.`$col` IS NULL OR TRIM(a.`$col`) = '')", []];
if ($kind === 'ref') return ["(a.`$col` IS NULL OR a.`$col` = 0)", []];
return ["a.`$col` IS NULL", []];
}
$fieldId = (int)substr($key, 7);
// A custom value row counts when any of its typed columns holds something
// (blank text does not); boolean false and number 0 are values.
return ["NOT EXISTS (SELECT 1 FROM asset_field_values v WHERE v.asset_id = a.id AND v.field_id = ?
AND ((v.value_text IS NOT NULL AND TRIM(v.value_text) <> '') OR v.value_number IS NOT NULL
OR v.value_date IS NOT NULL OR v.value_boolean IS NOT NULL OR v.value_ref_id IS NOT NULL))", [$fieldId]];
}Column names only ever come from BUILTIN, never from input, and the custom field id is a bound parameter.
findings() runs one query per asset type that expects something, selecting one 0/1 flag per expected field:
foreach ($keys as $i => $k) {
[$sql, $p] = self::missingSql($k);
// Missing, and not marked Not applicable for this asset.
$sel[] = "(($sql) AND NOT EXISTS (SELECT 1 FROM asset_field_not_applicable n WHERE n.asset_id = a.id AND n.field_key = ?)) AS m$i";
$params = array_merge($params, $p, [$k]);
}
$where = 'a.asset_type_id = ?' . ($hasRetired ? ' AND a.retired_datetime IS NULL' : '') . $tSql;
...
$stmt = $conn->prepare('SELECT a.id, a.hostname, a.asset_tag, ' . implode(', ', $sel) . " FROM assets a WHERE $where ORDER BY a.hostname, a.id");$tSql is activeTenantReadFilter($conn, $analystId, 'a') - the same company scope every asset list uses, including the All companies view (criterion 5). Retired assets are left out. A row is returned only when at least one flag is 1, with the missing keys in screen order (orderKeys(): the built-in order above, then custom fields by id).
Read it straight from SQL - every laptop with no purchase date and no exception:
SELECT a.id, a.hostname
FROM assets a
WHERE a.asset_type_id = 4
AND a.retired_datetime IS NULL
AND a.purchase_date IS NULL
AND NOT EXISTS (SELECT 1 FROM asset_field_not_applicable n
WHERE n.asset_id = a.id AND n.field_key = 'purchase_date');public static function saveExpected(PDO $conn, int $typeId, $keys): void
{
if (!self::ready($conn)) return;
$allowedCustom = array_column(self::customCandidates($conn, $typeId), 'key');
$clean = [];
foreach (is_array($keys) ? $keys : [] as $k) {
$k = (string)$k;
if (isset(self::BUILTIN[$k]) || in_array($k, $allowedCustom, true)) $clean[$k] = true;
}
$conn->prepare('DELETE FROM asset_type_expected_fields WHERE asset_type_id = ?')->execute([$typeId]);
...Unknown keys and custom fields not in the type's field sets are dropped, never stored. customCandidates() is the live fields of the sets attached through asset_type_field_sets.
save_asset_type.php calls it only when expected is in the request - like layout, so an older caller that saves just the name cannot wipe them:
if (array_key_exists('expected', $data)) {
AssetCompleteness::saveExpected($conn, (int)$id, $data['expected']);
}
β οΈ TRAP -get_asset_types.phphas two paths. A company's own types are rebuilt in a second array (scoped.own) for the settings dialog. The comment there already explains that icon and layout once got wiped because that array lacked them;expectedandexpected_customare added to it too. Leave either out and Save on a company's own type empties its expectations.
public static function setNotApplicable(PDO $conn, int $assetId, string $key, bool $on, int $analystId, string $label): void
{
if (self::sectionOf($key) === null) throw new InvalidArgumentException('Unknown field.');
if ($on) {
$stmt = $conn->prepare('INSERT IGNORE INTO asset_field_not_applicable (asset_id, field_key, set_by_analyst_id, set_datetime) VALUES (?, ?, ?, UTC_TIMESTAMP())');
$stmt->execute([$assetId, $key, $analystId ?: null]);
} else {
$stmt = $conn->prepare('DELETE FROM asset_field_not_applicable WHERE asset_id = ? AND field_key = ?');
$stmt->execute([$assetId, $key]);
}
// History only when something changed: marking a field twice is not two events.
if ($stmt->rowCount() > 0) {
$conn->prepare('INSERT INTO asset_history (...) VALUES (?, ?, ?, ?, ?, UTC_TIMESTAMP())')
->execute([$assetId, $analystId ?: null, 'Not applicable: ' . $label, $on ? null : 'Yes', $on ? 'Yes' : null]);
}
}It never touches the field (criterion 4). The endpoint checks requireModuleWriteJson('assets'), analystCanAccessAsset() and CSRF first.
Merges: AssetMergeService::REFERENCES gained ['asset_field_not_applicable', 'asset_id', 'unique', ['field_key']] - the mark moves to the kept asset unless it already has the same one. tests/asset-merge.php has a guard that fails when any column pointing at an asset is missing from that list; it caught this one.
api/assets/missing_info.php
| Request | Answers |
|---|---|
GET (?type_id= ?section= ?field=) |
rows [{asset_id, name, asset_tag, type, missing[]}], labels (every expected key β its name), sections, types, can_write
|
GET ?asset_id=N |
expected, missing, not_applicable [{key, by, at}], labels, can_write
|
POST {asset_id, field, not_applicable} |
the asset's new picture |
Built-in labels come from asset-management.missing.field_<key>; custom ones from asset_fields.label. can_write is analystModuleLevel(..., 'assets') === 'full' - levels are read and full.
-
Settings β Asset types β a type. The block is drawn only when the tables exist (
AssetCompleteness::ready()).expSetup(type, item)ticks fromitem.expectedand builds the custom ticks fromitem.expected_custom; Save sendspayload.expected = expCollect(). -
Header. The button shows when
AssetCompleteness::anyExpected()- oneLIMIT 1lookup - or on the page itself. -
Missing information page. One fetch; the type and field dropdowns fill on the first load; every chip has Not applicable for writers. Built with
textContentthroughout. -
The asset.
loadMissingNotice()runs when an asset opens and after every field save, so a filled field leaves the line at once. Hidden when the type expects nothing.
tests/asset-missing-info.php - 28 checks, ZZ fixtures removed in finally: nothing expected β nothing listed; unknown keys and out-of-set custom fields dropped; every expected field named; an asset still saves; 0 cost and dates filled in, spaces-only text and no supplier missing; custom field with and without a value, and a blank one; filling clears and clearing restores; changing expectations changes the list; Not applicable hides, leaves the field NULL, shows on the asset, writes one history line (not two for a repeat), and Undo restores; filters by field, section and type; retired assets left out.
Also run against the change: asset-merge (25), asset-type-layout (16), asset-custom-fields (29), asset-api-fields (27), asset-retirement (13), assets-all-companies (10), analyst-lifecycle (21).
- Findings are a query - never cache them in a column. The moment they are stored, every write route (page, import, REST, agent, merge) has to remember to refresh them, and the first one that forgets brings back the stale list the issue was written about.
-
A layout hiding a section is not Not applicable (the profiles design: "hidden by this profile, never not applicable"). The service never reads
asset_type_layout. -
Any new table with an
asset_idgoes intoAssetMergeService::REFERENCES- the merge test enforces it.
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