Repository navigation
Workflow Branching Developer Guide 2 Editor
Part 1: the engine Β· Part 2 of 3 Β· Part 3: safety, saving and tests Β· Workflow branching - design Β· GH #364
The engine side of branching is small; the editor is where the work is. The canvas was built for a straight line - every box free-floating, ordered by its height on screen - and a branch is a box that contains other boxes. This page explains how the editor models that, draws it, lets you click and edit what is inside, and writes it back.
| File | Change |
|---|---|
π‘ assets/js/workflow-editor.js
|
The branch model, drawing, clicks, detail panels, layout, save / load (?v=29) |
π‘ assets/js/workflow-executions.js
|
The execution log draws a branch and its path (?v=5) |
π΅ assets/css/workflow.css
|
.wf-br* styles, --wf-branch colour, dark mode (?v=14) |
π£ workflow/editor.php
|
Add branch button + menu; the wfBodyBranch detail panel |
π lang/*/workflow.php
|
workflow.branch.* (56 strings) and the help section, 9 languages |
workflow-editor.js keeps one array, nodes. Each node is {id, kind, x, y, el, ...} with kind one of trigger, condition, action. On save the conditions and the actions are each sorted by y - the order on screen is the order of execution - and written out. Connectors are not stored; they are drawn from that same sorted order.
A branch fits in by being one more kind of top-level node, branch, sorted in with the actions by y. Everything inside it is not a canvas node: paths, their conditions and their actions live inside the branch object and are drawn inside its box.
// branch {id, kind:'branch', type, field, compare, lanes[], parent?}
// lane {id, kind:'lane', role: branch|case|otherwise|default, label,
// match, values[], conds[], items[], parent: branch}
// items in a lane: {kind:'action', type, args, parent: lane} or a branch
// conds in a lane: {kind:'condition', field, op, value, parent: lane}
// Every item gets a local id; registry maps it back for findNode().
const BRANCH_TYPES = ['branch_if', 'branch_switch'];
const MAX_BRANCH_DEPTH = 3;
const registry = new Map();A lane is one path, drawn as a column. Its role says what it is: branch (an If branch), case, or the fallback - otherwise / default. The fallback is always the last lane.
Two design choices carry the rest of the editor:
-
Nested items reuse the existing kinds. An action inside a lane is
{kind: 'action', type, args}- the same shape as a canvas action node - and a condition is{kind: 'condition', field, op, value}. So the existing action and condition detail panels (showDetailForAction(),showDetailForCondition()) edit them unchanged: every action type's form, the merge-code picker, lookups, webhook test - all for free. -
Every item knows its
parent. That is how a delete knows which list to take it out of, and howdepthOf()counts nesting:
/** How many branches deep an item is (a top-level branch is 0). */
function depthOf(b) {
let d = 0, p = b.parent;
while (p) { if (p.kind === 'branch') d++; p = p.parent; }
return d;
}The old code looked up the selected node with nodes.find(x => x.id === selectedNodeId) in seven places. A nested item is not in nodes, so all seven now go through one function:
/** The selected thing by id: a canvas node, or anything inside a branch. */
function findNode(id) {
return nodes.find(x => x.id === id) || registry.get(id) || null;
}
/** Give an item an id and remember it. */
function reg(o) { o.id = nextLocalId--; registry.set(o.id, o); return o; }Ids are negative local numbers, the same counter the canvas already used (nextLocalId--), so a nested item's id can never collide with a node's.
β οΈ One lookup was missed at first and found by testing:selectNode()usednodes.find(x => x.id === id)-id, notselectedNodeId, so the search-and-replace skipped it. Clicking a path outlined it but opened nothing. A scripted click test caught it (the panel title stayed "Workflow"); it now callsfindNode(id).
The detail panels redraw what they edit with n.el.innerHTML = renderNodeContent(n). A nested item has no element of its own - it is drawn inside its branch - so every such call now goes through:
/** Redraw an edited item: its own element, or the branch box it sits in. */
function refreshNode(n) {
if (n && n.el && n.kind !== 'branch') { n.el.innerHTML = renderNodeContent(n); return; }
renderAll();
}renderAll() rebuilds the canvas but not the right-hand panel, so typing in a panel keeps its focus while the box updates.
Loading turns a stored branch into the model; saving turns it back. The two functions are exact inverses - the round-trip test in part 3 saves from the editor and checks the stored JSON is unchanged.
/** Engine shape -> editor model. */
function branchFromStored(a, parent) {
const args = a.args || {};
const b = reg({ kind: 'branch', type: a.type, field: args.field || '', compare: args.compare === 'contains' ? 'contains' : 'equals', lanes: [], parent });
const lane = (role, src) => {
const l = reg({ kind: 'lane', role, label: (src && src.label) || '', match: (src && src.match) === 'any' ? 'any' : 'all',
values: Array.isArray(src && src.values) ? src.values.map(String) : [], conds: [], items: [], parent: b });
((src && src.conditions) || []).forEach(c => l.conds.push(reg({ kind: 'condition', field: c.field || '', op: c.op || 'equals', value: c.value ?? '', parent: l })));
((src && src.actions) || []).forEach(x => l.items.push(itemFromStored(x, l)));
return l;
};
if (a.type === 'branch_if') {
(args.branches || []).forEach(br => b.lanes.push(lane('branch', br)));
b.lanes.push(lane('otherwise', args.otherwise || {}));
} else {
(args.cases || []).forEach(c => b.lanes.push(lane('case', c)));
b.lanes.push(lane('default', args.default || {}));
}
return b;
}
/** One stored entry inside a path -> an action item or a nested branch. */
function itemFromStored(x, lane) {
if (BRANCH_TYPES.includes(x.type)) return branchFromStored(x, lane);
return reg({ kind: 'action', type: x.type || 'log_message', args: x.args || {}, parent: lane });
}Note the fallback lane is pushed even when the stored branch has none - the editor can never show a branch without one.
/** Editor model -> engine shape. */
function branchToStored(b) {
const items = l => l.items.map(i => i.kind === 'branch' ? branchToStored(i) : { type: i.type, args: i.args || {} });
if (b.type === 'branch_if') {
return { type: 'branch_if', args: {
branches: b.lanes.filter(l => l.role === 'branch').map(l => ({ label: l.label, match: l.match,
conditions: l.conds.map(c => ({ field: c.field, op: c.op, value: c.value })), actions: items(l) })),
otherwise: { actions: items(b.lanes.find(l => l.role === 'otherwise') || { items: [] }) },
} };
}
return { type: 'branch_switch', args: {
field: b.field, compare: b.compare,
cases: b.lanes.filter(l => l.role === 'case').map(l => ({ label: l.label, values: l.values, actions: items(l) })),
default: { actions: items(b.lanes.find(l => l.role === 'default') || { items: [] }) },
} };
}Both recurse: a nested branch inside items goes back through branchFromStored() / branchToStored().
In loadWorkflow() and save():
// loadWorkflow(): a stored branch becomes a branch node
if (BRANCH_TYPES.includes(a.type)) { // GH #364
const b = branchFromStored(a, null);
b.x = snap(x); b.y = snap(y);
nodes.push(b);
...
}
// save(): branches are sorted in with the actions by y
const actionNodes = nodes.filter(n => n.kind === 'action' || n.kind === 'branch');
const actions = actionNodes
.slice().sort((a, b) => a.y - b.y)
.map(n => n.kind === 'branch' ? Object.assign(branchToStored(n), { x: n.x, y: n.y }) : ({ type: n.type, args: n.args || {}, x: n.x, y: n.y }));collectWorkflowForApi() (what the AI co-author is sent) does the same, so the AI sees the branch in the workflow it is asked to improve.
A canvas node is normally a fixed-size box (SIZE[kind]). A branch is as big as its content, so createNodeEl() hands it off:
if (n.kind === 'branch') return createBranchEl(el, n); // GH #364: sized by its contentfunction createBranchEl(el, n) {
registryRebuild();
el.innerHTML = branchHtml(n);
el.addEventListener('mousedown', e => onBranchMouseDown(e, n));
return el;
}branchHtml() builds the box as one string, recursively - a nested branch is branchHtml() called from inside a lane:
function branchHtml(b) {
const d = depthOf(b);
const head = b.type === 'branch_if'
? '<span class="wf-br-kind">' + esc(BT('if_title')) + '</span>'
: '<span class="wf-br-kind">' + esc(BT('switch_title')) + '</span> <span class="wf-br-field">' + esc((b.field || '?').split('.').pop()) + ' Β· ' + esc(b.compare === 'contains' ? BT('compare_contains') : BT('compare_equals')) + '</span>';
const lanes = b.lanes.map(l => {
const isDefault = l.role === 'otherwise' || l.role === 'default';
const items = l.items.map(i => i.kind === 'branch' ? branchHtml(i) : chipHtml(i)).join('') || '<div class="wf-br-empty">' + esc(BT('nothing_here')) + '</div>';
const addBranchBtns = d + 1 < MAX_BRANCH_DEPTH
? '<button type="button" class="wf-br-add-btn" data-add-branch="branch_if" data-lane="' + l.id + '">+ ' + esc(BT('add_if')) + '</button>'
+ '<button type="button" class="wf-br-add-btn" data-add-branch="branch_switch" data-lane="' + l.id + '">+ ' + esc(BT('add_choose')) + '</button>' : '';
return '<div class="wf-br-lane' + (isDefault ? ' is-default' : '') + '">'
+ '<div class="wf-br-lane-head" data-sel="' + l.id + '">...title + summary...</div>'
+ '<div class="wf-br-items">' + items + '</div>'
+ '<div class="wf-br-add"><button type="button" class="wf-br-add-btn" data-add-action="' + l.id + '">+ ' + esc(BT('add_action')) + '</button>' + addBranchBtns + '</div>'
+ '</div>';
}).join('');
return '<div class="wf-br' + (d ? ' is-nested' : '') + '"' + (d ? ' data-sel="' + b.id + '"' : '') + '>'
+ '<div class="wf-br-head"' + (d ? '' : ' data-head="1"') + '>' + head + '</div>'
+ '<div class="wf-br-lanes">' + lanes + '</div></div>';
}-
Every user-supplied string goes through
esc()(labels, field names, values) - the box is built as HTML, so this matters; ids are numbers the editor made. -
data-selmarks every clickable item with its registry id;data-headmarks only the top-level box's heading, which is the drag handle. - The depth limit is enforced in the UI by not drawing + If / + Choose in a lane already at depth 2. The save routes enforce it again (part 3).
- An action card is drawn by the same
renderNodeContent()a canvas action box uses (chipHtml()), so it shows the same title and one-line summary.
A canvas box is position: absolute. An absolutely positioned element with width: auto shrinks to fit - but never wider than the space left to the right edge of its containing block. A branch placed at x = 220 on a 1,200px canvas had at most ~980px, the columns were squeezed to share it, and a nested If inside a column spilled out of it. Ed saw it the first time he opened the demo.
/* assets/css/workflow.css */
/* GH #364: a branch box is as wide as its content needs. Positioned absolutely on the canvas,
its width would otherwise be capped by the space left to the canvas's right edge, squeezing
the lanes narrower than a nested branch inside them - which then spilled out of its lane. */
.wf-node-branch, .wf-br { width: max-content; }
.wf-br-lane { flex: 0 0 auto; min-width: 180px; }
.wf-br-chip, .wf-br-lane-head { max-width: 260px; box-sizing: border-box; }
.wf-br-add { flex-wrap: nowrap; }max-content lets the box grow to fit; the action cards and summaries are capped at 260px so a long message wraps instead of making one column enormous. The canvas grows to fit the box (updateCanvasSize()), so wide workflows scroll sideways.
The connectors and canvas sizing need a node's size; a branch's comes from its element after it is drawn:
/** A node's drawn size; a branch box is as big as its content. */
function sizeOf(n) {
if (n.kind === 'branch') {
return { w: (n.el && n.el.offsetWidth) || 360, h: (n.el && n.el.offsetHeight) || 220 };
}
return SIZE[n.kind];
}Every SIZE[n.kind] in the drawing code (lowestNodeY(), drawConnector(), updateCanvasSize()) now calls sizeOf(n).
Adding a path or an action makes the box taller, and a box that was placed with room under it can grow over the next action. renderAll() ends by moving anything now underneath a branch down below it:
/**
* GH #364: a branch box grows as paths and actions are added, so anything that now sits
* under it - in its columns - is moved down below it, in order. Only ever downwards and
* only what overlaps, so a layout somebody arranged is otherwise left as it is.
*/
function clearBranches() {
const sorted = nodes.filter(n => n.kind !== 'trigger').slice().sort((a, b) => a.y - b.y);
sorted.forEach(b => {
if (b.kind !== 'branch') return;
const bz = sizeOf(b);
let floor = b.y + bz.h + ROW_GAP;
sorted.forEach(n => {
if (n === b || n.y < b.y) return;
const nz = sizeOf(n);
const overlapsX = n.x < b.x + bz.w && n.x + nz.w > b.x;
if (overlapsX && n.y < floor) {
n.y = snap(floor);
if (n.el) n.el.style.top = n.y + 'px';
floor = n.y + nz.h + ROW_GAP;
}
});
});
}Moving a node changes the execution order only if it changes its rank by y - and it never does here: nodes only move down, in their existing order, past a branch that was already above them.
The canvas's own mousedown starts a drag. Inside a branch the same click might mean "drag the box", "select this action", "select this path" or "add an action here", so the branch has its own handler that decides first:
function onBranchMouseDown(e, n) {
const t = e.target;
const addA = t.closest('[data-add-action]');
const addB = t.closest('[data-add-branch]');
if (addA || addB) {
e.stopPropagation(); e.preventDefault();
const lane = registry.get(+(addA ? addA.dataset.addAction : addB.dataset.lane));
if (!lane) return;
let item;
if (addA) {
const type = Object.keys(window.WF_ACTION_DEFS)[0];
item = reg({ kind: 'action', type, args: newActionArgs(type), parent: lane });
} else {
item = newBranch(addB.dataset.addBranch, lane);
}
lane.items.push(item);
renderAll();
selectNode(item.id);
markDirty();
return;
}
const sel = t.closest('[data-sel]');
if (sel && !t.closest('[data-head]')) {
e.stopPropagation(); e.preventDefault();
canvas.focus({ preventScroll: true });
selectNode(+sel.dataset.sel);
return;
}
onNodeMouseDown(e, n); // the top-level head: drag the whole branch, or select it
}closest() finds the innermost marked element, so a click on an action card inside a nested If selects that card, not the If around it. A new action gets the first action type with its defaults (newActionArgs(), the same argDefault() rules Add action uses) and opens in the panel, ready to change.
Selection outlines use the same id: updateSelectionVisuals() also toggles .selected on every [data-sel] whose id is the selected one.
deleteSelected() (the Remove button and the Delete key) hands anything with a parent to deleteNested(), which enforces the rules the engine relies on:
function deleteNested(n) {
if (n.kind === 'lane') {
if (n.role === 'otherwise' || n.role === 'default') { window.showToast(BT('cannot_remove_default'), 'error'); return; }
const b = n.parent;
if (b.lanes.filter(l => l.role === n.role).length < 2) { window.showToast(BT(n.role === 'case' ? 'need_one_case' : 'need_one_branch'), 'error'); return; }
b.lanes = b.lanes.filter(l => l !== n);
...
} else if (n.kind === 'condition') {
if (n.parent.conds.length < 2) { window.showToast(BT('need_one_condition'), 'error'); return; }
...| Can't remove | Because |
|---|---|
| Otherwise / Default | Ed's rule: the fallback is always there |
| The last If branch / the last case | an If needs a branch, a Choose a case - the save routes refuse otherwise |
| A branch's last condition | a branch with no conditions never matches (part 1) |
The Otherwise / Default panel hides the Remove button altogether, so the refusal is rarely needed.
The right-hand panel gains one body, #wfBodyBranch, filled by two functions:
-
showDetailForBranch(b)- the whole branch: what it does, and for Choose the field (the trigger's fields, as for a condition) and match by (is one of, or contains - offered only for text fields). + Else if / + Case adds a path before the fallback:b.lanes.splice(b.lanes.length - 1, 0, l), which is what keeps Otherwise / Default last. Changing the field clears every case's values - a value picked for priority means nothing for requester email. -
showDetailForLane(l)- one path: its name, then for an If branch all / any and its conditions (each opens the ordinary condition panel), for a case its values - a tick-list when the field has fixed values (WF_LOOKUP_VALUES), otherwise one per line.
Conditions and actions inside a branch open the existing panels, because they have the existing shapes (section 2).
Both run views recurse through steps. The execution log page (workflow-executions.js):
if (kind === 'branch') {
const T = (k, p) => window.t('workflow.branch.' + k, p);
const cls = s.status === 'failed' ? 'bad' : 'ok';
let why = '';
if (s.type === 'branch_switch') {
why = '<div class="wfx-step-sub"><code>' + esc(s.field || '') + '</code> = <code>' + esc(JSON.stringify(s.actual ?? null)) + '</code>'
+ (s.reason === 'missing' ? ' - ' + esc(T('reason_missing')) : s.reason === 'no_match' ? ' - ' + esc(T('reason_no_match')) : '') + '</div>';
} else {
why = (s.checked || []).map(c => /* "Branch 1 "Urgent": matched subject contains "urgent" β" */ ...).join('');
}
const inner = (s.steps || []).map(renderStep).join(''); // recursion
return '<div class="wfx-step wfx-branch">'
+ '<div class="wfx-step-head"><span class="wfx-step-status ' + cls + '">' + esc(T(s.type === 'branch_switch' ? 'switch' : 'if')) + '</span>'
+ '<strong>' + esc(branchTakenText(s)) + '</strong></div>' + why
+ '<div class="wfx-branch-steps">' + (inner || '<div class="wfx-step-sub"><em>' + esc(T('nothing_to_do')) + '</em></div>') + '</div>'
+ '</div>';
}/** GH #364: "Took branch 2 "XYZ"", "Took Otherwise", "Took case 1", "Took Default" - the words for a branch's path. */
function branchTakenText(s) {
const T = (k, p) => window.t('workflow.branch.' + k, p);
const key = String(s.taken || '');
const label = s.taken_label ? ' "' + s.taken_label + '"' : '';
if (key.startsWith('branch:')) return T('took_branch', { n: +key.slice(7) + 1 }) + label;
if (key.startsWith('case:')) return T('took_case', { n: +key.slice(5) + 1 }) + label;
return T(key === 'otherwise' ? 'took_otherwise' : 'took_default');
}The stored index is zero-based; the screen says "case 2" (+ 1), matching the "Case 2" heading on the canvas. .wfx-branch-steps indents the path with a purple bar (--wf-branch).
The editor's Recent runs panel used to list a dry run's actions with step_log.filter(s => s.status === 'dry_run') - top level only, so actions inside a path would have vanished from the preview. It now walks the tree too (rowsFor(list, depth)), printing "Took case 1 "ABC Ltd"" above the path's previewed actions.
All under workflow.branch.*, read with window.t() (the page exports the workflow namespace). Placeholders: {n} in case_n, took_branch, took_case, branch_n. The help section's strings are workflow.help.branches_*. The 66 strings are in the 9 gated locales; the 8 translations were matched to each locale's existing words for workflow, condition, action and run history.
Continue: Part 3 - safety, saving and tests.
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
-
β³ π·οΈ 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
- β³ π§Ή 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