Repository navigation
Live Updates Developer Guide 2
How each screen follows other people's changes without throwing away what somebody is doing. Page 1 covers the design, the endpoint and the SQL behind every signature. User guide: Live updates.
assets/js/live-pulse.js is one IIFE that defines window.LivePulse. It is loaded on every analyst page by renderNotificationBell() (page 1 Β§3), after window.FREEITSM_LIVE = {seconds, url}.
const cfg = window.FREEITSM_LIVE || {};
const seconds = Number.isFinite(cfg.seconds) ? cfg.seconds : 15;
const url = (cfg.url || '') + 'api/system/pulse.php';
const watchers = new Map(); // topic -> Set(callback)
const sigs = new Map(); // topic -> last hash seen (undefined = not yet baselined)
let timer = null, inFlight = false, again = false, soonTimer = null;
let wroteSince = false; // this page saved something since the last checkasync function pulse() {
if (seconds <= 0 || !watchers.size || document.hidden) return; // off means off
if (inFlight) { again = true; return; }
inFlight = true;
const mine = wroteSince;
wroteSince = false;
try {
const topics = [...watchers.keys()];
const r = await fetch(url + '?topics=' + encodeURIComponent(topics.join(',')), { credentials: 'same-origin' });
const d = await r.json();
if (d && d.success && d.sig) {
for (const topic of topics) {
if (!(topic in d.sig)) continue;
const now = d.sig[topic];
const before = sigs.get(topic);
sigs.set(topic, now);
if (before === undefined || before === now || now === null) continue;
for (const cb of [...(watchers.get(topic) || [])]) {
try { cb(topic, { mine }); } catch (e) { console.error('[LivePulse]', topic, e); }
}
}
}
} catch (e) { /* offline or signed out: the next beat tries again */ }
inFlight = false;
if (again) { again = false; soon(400); }
}
/** Check shortly - collapses a burst of reasons into one request. */
function soon(ms) {
clearTimeout(soonTimer);
soonTimer = setTimeout(pulse, ms);
}-
First answer = baseline (
before === undefined): nothing runs. -
null(gone, or not allowed) is stored but never fires, so a ticket that was deleted doesn't loop. -
The callbacks are copied (
[...set]) before running, so a callback that stops watching doesn't disturb the loop. -
A background tab returns at once:
document.hidden.
| Trigger | Delay | Code |
|---|---|---|
| the timer |
seconds (15 / 30 / 60) |
setInterval(pulse, seconds * 1000), started by the first watch()
|
| a new topic is watched | 300 ms | baselines it, so a change right after drawing is not missed |
| the tab becomes visible, or the window gets focus | 150 ms |
visibilitychange, focus
|
| another tab of yours saved something | 700 ms |
BroadcastChannel poke (Β§2) |
| this page saved something | 1200 ms | the fetch wrapper (Β§2) |
| a beat arrived while one was running | 400 ms after it | again |
All except the timer go through soon(), so several reasons at once make one request.
function watch(topic, cb) {
if (!topic || typeof cb !== 'function') return () => {};
if (!watchers.has(topic)) { watchers.set(topic, new Set()); sigs.delete(topic); soon(300); }
watchers.get(topic).add(cb);
start();
return () => unwatch(topic, cb);
}
function unwatch(topic, cb) {
const set = watchers.get(topic);
if (!set) return;
set.delete(cb);
if (!set.size) { watchers.delete(topic); sigs.delete(topic); }
}
window.LivePulse = {
watch, unwatch, rebaseline, busyChip, clearChip,
now: () => soon(50),
enabled: () => seconds > 0,
seconds: () => seconds,
};rebaseline(topic) forgets the stored hash and checks within 300 ms, so the part adopts the current hash without its callback firing. Use it after redrawing from data you know is fresh.
const channel = typeof BroadcastChannel === 'function' ? new BroadcastChannel('freeitsm-live') : null;
if (channel) channel.onmessage = (e) => { if (e.data === 'poke') soon(700); };
const BACKGROUND_WRITES = /\/(pulse|ticket_presence|check_mailbox_email|scheduler_fallback|recent_trail_visit|set_user_preference|mark_read|clear)\.php$/;
const realFetch = window.fetch;
window.fetch = function (input, init) {
const method = String((init && init.method) || (input && input.method) || 'GET').toUpperCase();
const p = realFetch.apply(this, arguments);
if (method !== 'GET' && method !== 'HEAD') {
let target = '';
try { target = new URL(typeof input === 'string' ? input : input.url, location.href).pathname; } catch (e) { /* ignore */ }
if (target.includes('/api/') && !BACKGROUND_WRITES.test(target)) {
p.then(res => {
if (!res || !res.ok) return;
wroteSince = true;
if (channel) channel.postMessage('poke');
soon(1200); // others' screens settle on this; ours learns it was mine
}).catch(() => {});
}
}
return p;
};When a same-origin write to /api/ succeeds, three things happen:
-
wroteSince = true. The next beat reads it asinfo.mineand resets it. -
Your other tabs are poked. They are on the same browser and check within 700 ms.
BroadcastChannelnever leaves the browser, so nothing crosses analysts. - This page checks within 1200 ms, so it adopts the new hashes while they are still marked mine, instead of later mistaking them for someone else's change.
The wrapper never changes the request or the response; it only watches. The ticket workspace (ticket-workspace.js) wraps fetch too, to count writes in flight. live-pulse.js loads first, in the header, and the workspace wraps after it, so the chain is workspace β live-pulse β native.
mine is a hint, not proof. It means "this page wrote something since the last beat", not "the change was mine". If a colleague edits the open ticket in the same window as your own save, the beat counts as yours: the conversation still catches up, but their field change waits for the next change. That was accepted so that your own saves don't come back as a redraw or a false "someone else" prompt.
function busyChip(host, onRefresh) {
if (!host) return;
if (host.querySelector(':scope > .live-pulse-chip')) return; // one per host
const chip = document.createElement('div');
chip.className = 'live-pulse-chip';
chip.setAttribute('role', 'status');
chip.style.cssText = 'display:flex;align-items:center;gap:10px;margin:6px 0 8px;padding:6px 12px;border-radius:999px;'
+ 'background:rgba(37,99,235,.10);color:var(--text,#1e293b);font-size:13px;width:fit-content;max-width:100%;';
const msg = document.createElement('span');
msg.textContent = T('common.live.updated', 'Updated by someone else just now.');
const btn = document.createElement('button');
btn.type = 'button';
btn.className = 'btn btn-primary';
btn.style.cssText = 'padding:3px 12px;font-size:12px;';
btn.textContent = T('common.live.refresh', 'Refresh');
btn.onclick = () => { chip.remove(); onRefresh(); };
chip.append(msg, btn);
host.prepend(chip);
}- It is built from DOM nodes with
textContent, so a translation can't inject markup. - The colours use theme variables with a tint, so it reads in light and dark.
- A redraw of
hostremoves it with everything else. - Strings:
common.live.updated,common.live.refresh(en, de, es, pl, id).
The rule for every screen is the same: check busy; if busy, wait (lists) or show the prompt (open records); otherwise redraw without a spinner and put the scroll position back.
if (window.LivePulse) {
const listBusy = () => !!document.querySelector('#ticketContextMenu.active, .email-item.dragging, .ctx-sheet.active');
const listChanged = () => {
if (listBusy()) { setTimeout(listChanged, 2500); return; }
if (typeof refreshCurrentView === 'function') refreshCurrentView();
};
LivePulse.watch('tickets', listChanged);
}-
refreshCurrentView()is the β» button: folder counts plusloadEmails(). -
loadEmails()keeps the selection (it's state, not DOM). It is "last response wins" (loadEmailsToken), and in the table view it callsTicketTable.reload(), so the table follows too. - It redraws even for
mine: the list is cheap and safe. - The old once-a-minute marker check in the same script now runs only when live updates are off:
const marker = window.LivePulse?.enabled() ? null : await newestMarker();displayEmail() ends with liveWatchOpenTicket(email.ticket_id), and stopPresence() (the pane emptied) calls liveWatchOpenTicket(0).
let liveTicketId = 0, liveTicketStop = null;
function liveWatchOpenTicket(ticketId) {
ticketId = Number(ticketId) || 0;
if (ticketId === liveTicketId) return; // every redraw calls this; same ticket = nothing to do
if (liveTicketStop) liveTicketStop();
liveTicketStop = null;
liveTicketId = ticketId;
if (ticketId && window.LivePulse) {
liveTicketStop = LivePulse.watch('ticket:' + ticketId, (topic, info) => liveOpenTicketChanged(ticketId, info));
}
}
function liveTicketBusy() {
if (typeof ticketHasUnsavedInput === 'function' && ticketHasUnsavedInput()) return true; // reply / note open, chat text typed
if (ticketPendingWrites > 0) return true; // a save on its way
if (window.TicketWorkspace?.isActive() && TicketWorkspace.hasUnsavedWork?.()) return true; // property drafts
if (document.querySelector('.modal.active, #ticketContextMenu.active')) return true;
const a = document.activeElement;
const pane = document.getElementById('readingPane');
return !!(a && pane && pane.contains(a) && (a.matches('input, textarea, select') || a.isContentEditable));
}
async function liveOpenTicketChanged(ticketId, info) {
if (Number(currentEmail?.ticket_id) !== ticketId) return;
const busy = liveTicketBusy();
if (info.mine || busy) {
// Messages and replies can arrive while you write - show them; they never
// touch what you are typing.
if (document.getElementById('threadContainer')) {
loadCorrespondenceThread(ticketId, true);
loadTicketAttachments(ticketId);
}
if (busy && !info.mine) LivePulse.busyChip(document.getElementById('readingPane'), () => liveReloadTicket(ticketId));
return;
}
liveReloadTicket(ticketId);
}
async function liveReloadTicket(ticketId) {
try {
const d = await (await fetch(`${API_BASE}get_email_detail.php?ticket_id=${ticketId}`)).json();
if (!d.success || Number(currentEmail?.ticket_id) !== ticketId || liveTicketBusy()) return; // re-checked after the fetch
const pane = document.getElementById('readingPane');
const scrollers = [pane, ...pane.querySelectorAll('.tw-main, .tw-properties')];
const tops = scrollers.map(el => el.scrollTop);
displayEmail(d.email, d.recordings || []);
const after = [pane, ...pane.querySelectorAll('.tw-main, .tw-properties')];
after.forEach((el, i) => { if (tops[i]) el.scrollTop = tops[i]; });
} catch (e) { /* the next change tries again */ }
}| Situation | What happens |
|---|---|
| not busy, not mine |
liveReloadTicket(): no spinner (unlike loadTicketById()); scroll kept for the reading pane and both workspace columns |
| busy, someone else's change | the conversation catches up and the prompt appears |
| mine | only the conversation catches up: the part that saved already redrew |
-
The conversation always catches up because it is append-only: a customer's new WhatsApp message must appear while you're writing your reply. That is why the old chat timer now arms only without live updates:
if (currentTicketChannel !== 'email' && !window.LivePulse?.enabled()) { channelRefreshTimer = setInterval(() => { /* β¦ */ }, 15000); }
-
hasUnsavedWorkwas exported fromticket-workspace.jsfor this; it already backed the workspace's ownholdRender():requestPersonal, canLeave, holdRender, flushRender, hasUnsavedWork, // hasUnsavedWork: live updates (GH #267)
// DOMContentLoaded, after the first loadTasks() - not in an embedded editor (it returns earlier)
if (window.LivePulse) LivePulse.watch('tasks', liveBoardChanged);
function taskBoardBusy() {
if (dragState || document.querySelector('.col-dragging, .subtask-item.dragging')) return true;
const menu = document.getElementById('ctxMenu'); // TasksCtxMenu's card menu
return !!(menu && menu.style.display === 'block');
}
function liveBoardChanged() {
if (window.TASK_EMBED_CONTEXT) return;
if (taskBoardBusy()) { setTimeout(liveBoardChanged, 2500); return; }
loadTasks();
}loadTasks() redraws the board or list from api/tasks/list.php. The detail panel is separate DOM, so the board can redraw under an open task.
// openDetailPanel(), once drawn: liveWatchTask(taskId);
// closeDetailPanel(): liveWatchTask(0);
function taskPanelBusy() {
const panel = document.getElementById('detailPanel');
if (!panel) return false;
const a = document.activeElement;
if (a && panel.contains(a) && (a.matches('input, textarea, select') || a.isContentEditable)) return true;
if (document.getElementById('newCommentInput')?.value.trim()) return true;
if (descSaveTimer || (tinyEditor && typeof tinyEditor.hasFocus === 'function' && tinyEditor.hasFocus())) return true;
if (panel.querySelector('.tf-frame') || document.querySelector('.modal.active, .modal-overlay.active')) return true;
return taskBoardBusy();
}
async function liveTaskChanged(taskId, info) {
if (selectedTaskId !== taskId || info.mine) return; // ours: the panel already shows it
const panel = document.getElementById('detailPanel');
const body = panel?.querySelector('.detail-panel-body') || panel;
if (taskPanelBusy()) { LivePulse.busyChip(body, () => liveRedrawTask(taskId)); return; }
liveRedrawTask(taskId);
}
async function liveRedrawTask(taskId) {
const panel = document.getElementById('detailPanel');
const body = panel?.querySelector('.detail-panel-body') || panel;
const top = body ? body.scrollTop : 0;
await openDetailPanel(taskId); // which scrolls to the top on every open
const after = document.getElementById('detailPanel')?.querySelector('.detail-panel-body') || document.getElementById('detailPanel');
if (after && top) after.scrollTop = top;
}-
The open task ignores
minewhere the open ticket doesn't. Task fields save themselves on change, so each of your own saves would otherwise come back as a redraw while you move to the next field. -
descSaveTimeris the description's debounced save. Redrawing before it fires would destroy the TinyMCE instance holding the unsaved text.
poll();
setInterval(poll, 60000);
// GH #267: a new notification shows within one heartbeat (15 seconds by default),
// not the next minute. The minute poll stays: it also starts the scheduler (#233).
if (window.LivePulse && !cfg.portal) window.LivePulse.watch('notifications', () => poll());The portal bell never loads live-pulse.js, so window.LivePulse is undefined there. poll() is the bell's existing count request, which also paints the badge and plays the chime.
'live_updates' => '15', // in $prefDefaults: '15', '30', '60' or '0'const liveSelect = document.getElementById('liveUpdatesSelect');
if (liveSelect) {
let savedLive = liveSelect.value;
liveSelect.addEventListener('change', async () => {
liveSelect.disabled = true;
if (await savePref('live_updates', liveSelect.value)) savedLive = liveSelect.value;
else liveSelect.value = savedLive;
liveSelect.disabled = false;
});
}includes/preference_templates.php lists it as section live-updates, so preference templates can carry it (tests/preference-templates.php fails for a page key in neither list). It applies from the next page load, because FREEITSM_LIVE is printed by the server.
TRAP: housekeeping writes are not "mine". The presence heartbeat (
ticket_presence.php) posts every 10 seconds. While it counted as a write, every beat wasmine, so the open ticket never followed anybody else's change: the list updated and the pane did not. Found by the headless check (Β§6). A new background writer goes inBACKGROUND_WRITES.
TRAP: re-check busy after the fetch.
liveReloadTicket()fetches first and redraws after, and you may have started typing in between. It callsliveTicketBusy()again beforedisplayEmail().
TRAP:
openDetailPanel()scrolls to the top. A live redraw that called it bare would jump the panel back to the top every time a colleague commented.liveRedrawTask()saves and restores the scroll position.
TRAP: lists retry, records prompt. A list that is busy only because a menu is open will be free in a moment, so it retries every 2.5 s. An open record that is busy may stay busy for minutes (a long reply), so it shows the prompt instead of retrying for ever.
TRAP: embedded task editors. A task inside a ticket's Work tab is
tasks/embedded.phpin a frame, with no header, so it has noLivePulse.liveBoardChanged()returns early forTASK_EMBED_CONTEXTas well.
Done for 5.0.0 on a test install with headless Chrome. The harness lives outside the repo; this is its shape. A separate PHP script plays "somebody else", so the page can't count the change as its own:
// zz267change.php - in the test install, removed afterwards
$p = new PDO(/* the throwaway database */);
$p->prepare("UPDATE tickets SET subject = ?, updated_datetime = UTC_TIMESTAMP() WHERE id = ?")
->execute(['ZZ267 renamed by someone else', $ticketId]);<!-- zz272harness.html: the real page in a frame; the harness's own fetch is not wrapped -->
<iframe id="f" src="tickets/?ticket_id=1451"></iframe>
<script>
f.onload = () => setTimeout(async () => {
const d = f.contentWindow.document;
// the busy variant: f.contentWindow.openNoteModal(); d.getElementById('noteText').textContent = 'half-written note';
await fetch('zz267change.php');
setTimeout(() => {
const listHas = [...d.querySelectorAll('.email-item')].some(r => r.textContent.includes('ZZ267 renamed'));
const paneHas = d.getElementById('readingPane').textContent.includes('ZZ267 renamed');
document.title = 'list=' + listHas + ' pane=' + paneHas + ' chip=' + !!d.querySelector('.live-pulse-chip');
}, 20000);
}, 4000);
</script>chrome --headless=new --user-data-dir=<throwaway profile> --virtual-time-budget=40000 --dump-dom http://localhost/<install>/zz272login.php
| Check | Result |
|---|---|
| Rename the open ticket |
list=true pane=true (before the BACKGROUND_WRITES fix: list=true pane=false) |
| The same, with a half-written note |
pane=false chip=true, and the note and its text were kept |
| Rename the open task and another card | the card shows the new title, and the task's title input has the new value (read input.value; textContent doesn't include it) |
Delete the throwaway profile afterwards, never every Chrome process.
-
Server: add
livePulse<Thing>()and a branch inlivePulseSignatures(). See page 1 Β§5 for the pattern, and gate and scope it exactly like the list it stands for. -
Watch it:
function changesChanged() { if (changesBusy()) { setTimeout(changesChanged, 2500); return; } // a list: wait loadChanges(); } const stop = LivePulse.watch('changes', changesChanged); // an open record: LivePulse.watch('change:' + id, (t, info) => { // if (info.mine) return; // if (recordBusy()) return LivePulse.busyChip(container, () => redraw(id)); // redraw(id); // no spinner, scroll restored // });
-
Write the busy rule for that screen: focused fields, open modals and menus, drags, writes in flight, unsaved drafts.
-
Test both halves: the signature in
tests/live-pulse.php, and a headless check where a separate script makes the change.
Not wired yet: the Changes, Problems and Assets lists and their open records.
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)
- β³ π οΈ 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: Chart of accounts
- β³ π§βπΌ REST API: Analysts
- β³ πΊοΈ REST API: Network Mapper
- β³ π§ Using the API docs page
- β³ π OpenAPI specification
- β³ β OpenAPI: kept correct
- β³ π οΈ Maintaining the catalogue
- Watchtower
-
Tickets
- β³ π Live updates
- β³ π οΈ Watching a ticket - Developer Guide (1 of 2)
- β³ π οΈ 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
- β³ π οΈ 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
- β³ π Ticket dashboard β Developer Guide
- β³ Mailbox Authentication
- β³ π€ Email send log
- β³ π 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)
- β³ π οΈ 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
- β³ β 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
- β³ π’ 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
- β³ π οΈ CMDB β Developer Guide
- β³ π οΈ Impact analysis β Developer Guide
- β³ π οΈ Data quality β 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
- β³ β° 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
- β³ π οΈ Preferences β Developer Guide
- β³ π§Ή Maintenance
- β³ π Finding people in the Analysts list
- β³ πͺ When an analyst leaves
- β³ π οΈ System β Branding β Developer Guide
- β³ π©Ί Page health (D019) β Developer Guide
- β³ β Feature Bingo
- β³ π·οΈ 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
- β³ π 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