Repository navigation
Help Assistant Developer Guide
How the help assistant works under the hood. The plan, the decisions and the reasoning are on The help assistant - design; this page covers what is built.
| Step | What | State |
|---|---|---|
| 1 | One shared embedding file | β Embeddings - Developer Guide |
| 2 | The help index and word search | β this page |
| 3 | System β Help assistant and the window (no-AI level) | not yet |
| 4 | Vectors | not yet |
| 5 | Ask - the written answer | not yet |
| 6 | Unanswered questions | not yet |
Nothing is on screen yet. Step 2 is the engine the window will sit on.
| File | What it does |
|---|---|
includes/help_index.php |
The pages, reading a rendered page, building the index, the search |
scripts/help_render_page.php |
Renders ONE help page in ONE language and prints its sections as JSON |
scripts/help_index_build.php |
Builds or refreshes the index from the command line |
help_sections |
The index - only a cache of the help, one row per section per language |
includes/i18n.php |
I18n::pinLocale() - fixes the language for a command-line render |
tests/help-search.php |
The tests and the question set |
php scripts/help_index_build.php # English
php scripts/help_index_build.php --locales=de,es # plus German and Spanish
Every help page already marks its sections the same way, so that markup is the contract - no new markup was needed:
<div class="help-section" id="settings" data-cap="TICKETS_SETTINGS" data-help-search="off">
<div class="help-section-header">
<span class="help-section-num">10</span>
<div><h3>Settings</h3> <p>...</p></div>
</div>
<div class="help-cards">
<div class="help-card"><strong>Departments</strong><span>Create departments like IT...</span></div>
</div>
</div>| Part | Becomes |
|---|---|
id |
the anchor an answer links to - tickets/help.php#settings
|
the first <h3>
|
the title |
| everything inside | the text, kept as blocks - one per paragraph, card, step, note, list item, table row |
data-cap (optional)
|
the capability (Cap enum) the section describes - for permission-aware answers in step 5 |
data-help-search="off" (optional)
|
never indexed |
The number badge, <script> and <style> are left out. A section without an id is ignored.
Plus one entry for the page's introduction - its .help-hero banner and any .help-lede paragraph outside the sections, titled by the hero's (or the page's) <h2>. It has no anchor (section_key is the page itself), so it links to the top of the page, and it is often the best answer to "what is X?". An audit of all 74 pages (November 2026) found no section without an id and no help text outside a section other than these introductions. This is written into Help page house style, and tests/help-search.php fails if any help page gives no sections.
data-cap is read and stored now; the marks themselves go onto the pages with step 5, when answers start using them.
The obvious approach - read each page's source for t('...') keys - does not work:
- Many pages build their sections in a loop through helpers (
$h($id . '.title')inpeople/help.php), so the keys never appear literally. - The System help pages are English in the page itself, with no keys at all.
So every page is rendered, exactly as a reader would see it, and the sections are read out of the HTML (helpRenderSections(), using DOMDocument).
function helpIndexRenderPage(string $root, string $php, string $page, string $locale, int $analystId): ?array
{
$cmd = escapeshellarg($php) . ' ' . escapeshellarg("$root/scripts/help_render_page.php") . ' '
. escapeshellarg($page) . ' ' . escapeshellarg($locale) . ' ' . (int)$analystId;
exec($cmd . ' 2>' . (stripos(PHP_OS_FAMILY, 'Windows') === 0 ? 'NUL' : '/dev/null'), $out, $code);
// ...the last non-empty line is the JSON
}TRAP: never render two help pages in one PHP process. Pages define functions and constants, call
session_start()and mayexit()- the second would collide with the first, or never run.help_render_page.phprenders one, prints JSON from a shutdown function (so it is printed even when the page exits), and ends.
The renderer gives the page an ordinary signed-in GET:
I18n::pinLocale((string)$locale); // the page's own initFromSession() cannot change it
session_id('helprender' . bin2hex(random_bytes(8))); // a throwaway session, destroyed at the end
session_start();
$_SESSION['analyst_id'] = (int)$analystId;
parse_str($query, $_GET); // system/integrations/help.php?provider=jira
ob_start();
register_shutdown_function(function () {
$html = '';
while (ob_get_level() > 0) $html = ob_get_clean() . $html;
@session_destroy();
echo "\n" . json_encode(['ok' => true, 'sections' => helpRenderSections($html)], ...) . "\n";
});
chdir(dirname("$root/$page"));
require "$root/$page";-
The analyst is an active administrator with every module (
helpIndexRenderAnalyst()), only so each page's ownrequireModuleAccess()lets it through. Nothing is written for them - help pages do not touch the Recent trail. -
The language: a page calls
I18n::initFromSession(), which reads the analyst's saved preference.I18n::pinLocale()- command line only, it does nothing in a web request - makes that call leave the locale alone. -
It is command-line only (
PHP_SAPI !== 'cli'β 404), and the page argument must match the help-page pattern, so it cannot be pointed at anything else.
helpIndexPages(): every */help*.php and */*/help*.php that calls requireModuleAccess('...') (its module), every system/help/*.php except _*.php and index.php (module system), plus HELP_INDEX_EXTRA - the integrations guide, one page per ?provider=, which the folder scan cannot find. Left out on purpose (HELP_INDEX_EXCLUDE): the self-service portal's guide and Help Centre, which are for requesters. Today: 74 pages, 712 entries - 639 sections plus 73 page introductions.
helpIndexBuild($conn, $locales) renders every page in English, then each extra language:
| Unchanged section | left alone - its row, and later its vector, are kept (text_hash matches) |
| Changed section | updated |
| Section gone from its page | deleted; a page that no longer exists takes its sections with it |
| Another language | stored only where the text differs from the English - an untranslated section would be a second copy of the English, so the System help pages (English in the page) never get "German" rows |
| A module switched off | skipped, its rows left alone - nobody can open it, so the search never returns them |
An unchanged rebuild changes nothing (tested). English takes about 25 seconds for 74 pages; English, German and Spanish about 80.
help_sections:
CREATE TABLE IF NOT EXISTS `help_sections` (
`section_key` VARCHAR(191) NOT NULL, -- 'tickets/help.php#settings'
`locale` VARCHAR(10) NOT NULL DEFAULT 'en',
`page`, `anchor`, `module`, `cap`, `title`, `body`,
`text_hash` CHAR(64) NOT NULL, -- sha256 of title + body: what it says now
`embedding` MEDIUMTEXT NULL, -- step 4
`embedding_hash` CHAR(64) NULL, -- the text_hash the vector was made from
`embedding_model` VARCHAR(80) NULL,
`source` VARCHAR(20) NOT NULL DEFAULT 'built', -- or 'release'
`source_version` VARCHAR(20) NULL,
`built_datetime` DATETIME NOT NULL,
UNIQUE KEY `uq_help_sections_key_locale` (`section_key`, `locale`),
KEY `idx_help_sections_locale_module` (`locale`, `module`)
);embedding_hash is how the out-of-date warning will work: a section whose text_hash is not its embedding_hash has changed since its vector was made.
helpSearch($conn, $analystId, $question, $locale, $currentModule) = helpRank(helpSectionsFor(...), ...).
Every section in the analyst's language where there is one, otherwise its English row - the fallback is per section, so a half-translated language never hides the other half. Then only modules the analyst can open (analystCanAccessModule(), which also says no to a module switched off for the install).
Lower case; letters and digits only; common English words dropped (how, do, I, a, the...); then a cut-down Porter stemmer. It only has to be consistent - the question and the help go through the same rules - not produce real words:
| In | Out |
|---|---|
| departments | department |
| categories | category |
| statuses, status | status |
| adding, added, adds, add | add |
| settings, setting | set |
| create, created, creating | creat |
| route, routing | rout |
| breached | breach |
| class, analysis, business | unchanged |
Non-English words are only lower-cased.
BM25 is the classic search-engine scoring. For each question word t in a passage d:
with kβ = 1.2 and b = 0.75. In words: rare words count for more (ticket is in most sections and says little; department narrows it right down), a word appearing more often helps but with diminishing returns, and a long passage does not win just by being long. Title words count three times (HELP_TITLE_WEIGHT).
TRAP: score passages, not whole sections. The first build scored whole sections, and the very first test question - how do I create a ticketing department - missed. Tickets β Settings is about 10,000 characters of cards (the average section is 1,500), and BM25's length rule, correctly, buried its one Departments card. Now each section is cut into passages of about 700 characters made of whole blocks (
helpPassages()- the renderer's blank-line-separated blocks, packed in order, never splitting a card), passages are scored, and a section scores as its best passage, with that passage as the snippet.
foreach ($sections as $i => $s) {
$titleTokens = helpTokens($s['title']);
foreach (helpPassages($s['body']) as $text) {
$tokens = array_merge(...array_fill(0, HELP_TITLE_WEIGHT, $titleTokens), ...[helpTokens($text)]);
// ...term frequencies, document frequencies over PASSAGES
}
}
// ...each section keeps its best passage's score
if ($currentModule !== null && $s['module'] === $currentModule) $score *= HELP_MODULE_BOOST; // 1.15 - a tie-breakerAbout 80 ms over 712 entries on a laptop, all in PHP.
tests/help-search.php holds 65 realistic questions, each with every section that would be a right answer, scored as is a right section in the top 5:
| Kind | Example | Word search |
|---|---|---|
| Plain | how do I create a ticketing department | 43/47 (91%) - floor 80% |
| Exact names | Warbot, MoSCoW, Enforce approvals | 6/6 (100%) - floor 80% |
| Vague - no words shared with the answer | my boss wants a weekly PDF of how we are doing | 2/6 (33%) |
| Other languages | Wie erstelle ich eine Abteilung?, Hogyan hozzak lΓ©tre jegykezelΕ rΓ©szleget? | 2/6 (33%) |
Plain and exact questions must stay above their floor. Vague questions and other languages are reported, not failed - they are exactly what vectors (step 4) and the AI's own searching (step 5) are for, and these numbers are the baseline those steps have to beat. Typical misses, and why:
- my boss wants a weekly PDF β the answer is Report packs; no word in common.
- Wie erstelle ich eine Abteilung? β the German help says Abteilungen; there is no German stemming.
- Restablecer la contraseΓ±a de un analista β the answer is System help, which is English only.
- Hungarian and Polish β no help in those languages, so no words to match at all.
tests/help-search.php:
-
No database (19 checks): reading sections from rendered HTML (only sections with an id, the page's introduction, the h3 title without the number badge, a card's title not glued to its body, scripts left out,
data-cap,data-help-search="off"); search words and the stemmer; passages made of whole blocks of at most 700 characters; one card in a very long section winning, with that card as the snippet; the module tie-breaker. -
With
FREEITSM_TEST_DATABASE: builds English, German and Spanish through the real renderer; every help page gives sections; every section has a title; German rows only where the text is German (none for System help); an unchanged rebuild changes nothing; a ZZ analyst with only Tickets is searched over Tickets help only (control: an administrator gets every module); then the question set.
php tests/help-search.php
FREEITSM_TEST_DATABASE=<the throwaway db> php tests/help-search.php
See also Developer Tests - Knowledge.
- The help assistant - design
- Embeddings - Developer Guide - step 1, and what step 4 builds on
- Help page house style - the markup the index reads
- Internationalisation (i18n)
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
- β³ π 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 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
-
β³ π·οΈ 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
- 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
- β³ π οΈ 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
- β³ π§Ή 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
- β³ π± #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
- β³ π§© #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
- β³ ποΈ #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