Repository navigation
API Uploads and Knowledge Documents Design
Status: design agreed by Ed, 21 November 2026 (decisions); waiting for @Dr4inder's view on #416; to be built in 5.10.0. Issues: #417 (picture size) and #416 (article documents), both from @Dr4inder. #417's first part - the size setting, GET /knowledge/images/constraints and 413 image_too_large - is already built for 5.9.0 (REST API - Knowledge); this page is what comes after it.
In one paragraph: files up to now reach the API in one request - a picture as base64 inside JSON, a project document as a multipart form. Both hit limits the integration cannot see or change: PHP's upload_max_filesize (2 MB by default), post_max_size (8 MB by default), PHP's memory, and any proxy in front (nginx refuses anything over 1 MB by default). This design adds one upload API for every file: start an upload, send it in pieces, then hand it to the record that wants it. Pieces fit under every one of those limits, a dropped connection resumes instead of starting again, and the server holds a piece at a time instead of the whole file. Article documents (#416) are the first new thing built on it.
- Why chunks
- The upload API
- Handing an upload to a record
- Documents on Knowledge articles (#416)
- Security and housekeeping
- What changes for existing clients
- Decisions
- How it will be tested
| base64 JSON (pictures today) | multipart form (project documents today) | chunks (this design) | |
|---|---|---|---|
PHP upload_max_filesize
|
not applied | hard limit - 2 MB by default | not applied |
PHP post_max_size
|
read anyway, but PHP warns on every one | hard limit - 8 MB by default | each piece is far below it |
| A proxy body limit (nginx: 1 MB) | refused | refused | pieces sized to fit |
| Memory on the server | ~5 x the file | ~1 x | one piece |
| Bytes on the wire | +33% | the file | the file |
| Connection drops at 90% | start again | start again | carry on from 90% |
| Calls | 1 | 1 | 3 or more |
FreeITSM already works this way in one place: the Files module sends a 2 GB file from the browser in 4 MB pieces (api/files/upload.php). This design gives the REST API the same mechanism, and the big platforms use the same shape - Microsoft Graph upload sessions, Google resumable uploads, S3 multipart, tus.
The one-call routes stay. Chunks are for files that are big, or servers whose limits are small; a 200 KB screenshot can still go up in one request.
POST /api/v1/uploads start
PUT /api/v1/uploads/{upload_id}?offset=N one piece (raw bytes)
GET /api/v1/uploads/{upload_id} how much has arrived - to resume
DELETE /api/v1/uploads/{upload_id} give up
GET /api/v1/uploads/limits every purpose's size and type limitsPOST /api/v1/uploads
{ "purpose": "knowledge_document", "filename": "Network runbook.pdf", "size": 48318921,
"sha256": "9f2cβ¦" }201 { "data": { "upload_id": "u_5e1f0cβ¦", "purpose": "knowledge_document", "size": 48318921,
"received": 0, "chunk_bytes": 4194304, "expires_at": "2026-11-22T14:05:00Z" } }-
purposesays what the file is for:knowledge_imageorknowledge_documentto begin with (laterticket_attachment,project_documentβ¦). The purpose decides who may start (the key needs that purpose's create permission - no new permission to grant), how big (the purpose's own limit, checked now, before a byte is sent) and which types (the extension is checked now; the content again at the end). -
sha256is optional. When given, the assembled file must match it or the upload is refused. -
chunk_bytesis the largest piece this server takes: 4 MB, or less where PHP'spost_max_sizeis smaller. A client behind a stricter proxy simply sends smaller pieces - any size up tochunk_bytesis fine.
PUT /api/v1/uploads/u_5e1f0c�offset=0
Content-Type: application/octet-stream
<4194304 raw bytes>200 { "data": { "upload_id": "u_5e1f0cβ¦", "received": 4194304, "size": 48318921, "complete": false } }-
Raw bytes, not multipart and not base64 -
upload_max_filesizenever applies, nothing is encoded, and the piece is streamed straight to disk. -
In order.
offsetmust equal what has arrived so far. Anything else is409 offset_mismatchwithreceivedin the reply - so a client that lost track just asks, and carries on from there. A piece is never written twice. -
The last piece brings
receivedtosizeand the reply says"complete": true. Too many bytes is refused.
GET /uploads/{upload_id} returns received, size and expires_at - after a dropped connection, send from received. DELETE throws the pieces away. An upload not finished within 24 hours of its last piece expires and its pieces are deleted.
GET /api/v1/uploads/limits
{ "data": { "chunk_bytes": 4194304, "purposes": {
"knowledge_image": { "max_bytes": 10485760, "formats": [ { "extension": "png", "mime_types": ["image/png"] }, "β¦" ] },
"knowledge_document": { "max_bytes": 10485760, "formats": [ "β¦ the install's attachment types β¦" ] } } } }GET /knowledge/images/constraints (5.9.0) stays, and reports the same picture limits.
A finished upload is not a document or a picture yet - it is bytes waiting. The record that wants it takes it by id, in the same call that would otherwise carry the file:
POST /api/v1/knowledge/articles/812/images
{ "upload_id": "u_5e1f0cβ¦", "filename": "diagram.png", "client_reference": "old-kb:img:881" }At that moment, and only then, everything the one-call route checks is checked: the article exists and the key may write to it, the purpose matches, the size is within the limit now (an administrator may have lowered it meanwhile), the content really is an allowed type (magic bytes; never SVG), the SHA-256 if one was given. The file then moves into its store - the same random name, the same protected folder, the same audit - and the upload is used: it cannot be handed to a second record.
Retries are safe. An upload remembers what it became for 24 hours, so sending the same upload_id and client_reference again returns the same picture or document (HTTP 200, replayed: true) instead of an error. A different client_reference with a used upload is 409 upload_used. And the existing rule still holds across new uploads: the same client_reference with the same bytes is a replay; with different bytes it is 409 reference_conflict.
Article documents - the PDFs and Office files in an article's Documents panel, and the ones customers can download from the Help Centre - are not in the API today. They will be, reusing DocumentsService, the code behind the Documents panel and the project-documents API (#287), so the app and the API cannot drift.
| Route | Permission | Does |
|---|---|---|
GET /knowledge/articles/{id}/documents |
knowledge_documents.read |
Paged list, metadata only: id, kind (file / link), title, description, filename, MIME type, size, sha256, external URL, show_in_help_centre, client_reference, uploaded by and at, url (below) and content_url. Every document on the article, whether or not the article's HTML links to it. ?client_reference= finds an earlier upload without sending it again. |
POST /knowledge/articles/{id}/documents |
knowledge_documents.create |
A file - upload_id (any size), or a multipart file as projects take it (small files) - or a link, external_url. With title, description, client_reference, show_in_help_centre. 201; 200 for a replay; 409 for a reused reference. |
POST /knowledge/articles/{id}/documents/{document_id}/link |
knowledge_documents.create |
Attach a document that already exists - the key's analyst must already be able to see it. |
PATCH /knowledge/articles/{id}/documents/{document_id} |
knowledge_documents.create |
title, description, show_in_help_centre. |
GET /knowledge/articles/{id}/documents/{document_id}/content |
knowledge_documents.read and documents.download
|
The bytes, through the download guard - counted, alerted, logged with the key - exactly as project documents. A link returns its URL as JSON. |
DELETE /knowledge/articles/{id}/documents/{document_id} |
knowledge_documents.delete |
Removes this article's link. A document still attached elsewhere stays; the last link soft-deletes it, as in the app. |
Access is the article's. A document on an article inherits every rule the article has - company, audience, access list, and whether it is published - through includes/knowledge/visibility.php, as it already does in the app. An article the key cannot reach is 404, and a document that is not on that article is 404: no document is ever served by id alone, and knowing a document's URL never gets round the article. Revoking someone's access to the article stops their downloads at once.
The url for article HTML is the app's own document link, which re-checks the reader on every request - an analyst's or portal user's session, never an API key - so a migrated article can link to its PDF the way a hand-written one does. Nobody signed in gets nothing, as with pictures.
Limits and types are the install's attachment settings (System β Attachments: 10 MB and the usual list by default), reported by GET /uploads/limits.
What happens around an upload, stated so a migration can stage drafts predictably:
| Search | The title is searchable at once; the text of a PDF or Office file is extracted in the background, as in the app. Search shows a document only to people who can see its article. |
| Help Centre | Off unless show_in_help_centre: true, and customers see it only once the article is published, customer-facing and theirs. Turning it on is the same "widens who can read it" act as attaching, so it needs knowledge_documents.create. |
| AI and embeddings | Documents are not sent to an AI provider and do not change the article's embedding. |
| Workflows and notifications | None. Attaching a document does not trigger a workflow or a notification. |
| Article revision | Attaching, detaching and changing a document will change the article's revision, so a later PATCH with a stale expected_revision is refused. Today the revision covers the article's pictures but not its documents; this adds them. |
| Audit | Recorded on the article, by the key's analyst, as pictures are. |
-
An upload belongs to the key that started it. Another key - even one acting as the same analyst - gets 404.
upload_idis 32 random characters, never a counter. -
Pieces are never reachable over the web. They collect in a protected store (
uploads/api-incoming/, registered inincludes/file_stores.phplike every other store, denied by the web server and checked bytests/web-exposure-guard.php). Only the hand-over moves a file out. -
No filling the disk. A key may have at most 10 unfinished uploads, each no bigger than its purpose allows, and expired ones are deleted - on every
POST /uploads(so no scheduled job is needed) and by the nightly cron where there is one. - Rate limits count each piece like any other request. A 50 MB file in 4 MB pieces is 14 requests; the default per-minute limit leaves room, and a key moving thousands of files can be given a higher limit on System β API.
-
Memory stays flat. A piece is streamed from
php://inputto the file, never held whole; the hand-over hashes the file in a stream.
Nothing breaks. The base64 picture upload keeps working for small pictures; project documents keep taking a multipart file. Both routes also accept upload_id, so a client can move to chunks one endpoint at a time.
Decided - Ed, 21 November 2026 ("all this sounds good"):
-
Permissions - an upload needs its purpose's create permission; there is no separate
uploads.create. A key that may add a picture may upload one, and nobody has another box to tick. -
Article documents' permissions - their own
knowledge_documents.read/create/delete, as pictures haveknowledge_images.*and as #416 asks ("narrowly scoped"). -
Help Centre through the API -
show_in_help_centrecan be set on create and PATCH; a migration otherwise needs a person to click through every article. - Expiry - 24 hours after the last piece, fixed; revisited if anyone asks.
- Release - 5.9.0 ships first, as it is; this goes in 5.10.0.
Not affected: the one-request limit. The size an administrator chooses (Knowledge β Settings β Images, up to 50 MB) applies to the one-request base64 route too - a 50 MB picture went up in one request, replayed and downloaded byte for byte on the test install (21 Nov 2026) once its PHP allowed it (memory_limit 512M, post_max_size 128M). Chunks are for when the server's limits are smaller, not a requirement.
Against a throwaway install, with synthetic files, as tests/knowledge-migration-api.php already is:
- a 30 MB file in pieces assembles byte for byte; a piece at the wrong offset is 409 with
received; resuming after a "dropped" piece finishes the file; a wrongsha256is refused at the end - a purpose's size and extension are refused at start, and the content type again at hand-over; SVG and a PHP file renamed
.pngnever land - another key cannot read, send to or hand over someone else's upload; a used upload cannot be handed over twice; a replay with the same reference returns the same record
- pieces are never served over HTTP; ten unfinished uploads per key and no more; an expired upload's pieces are gone
- #416's acceptance: a restricted draft gets one file (via chunks) and one link; both appear in the native Documents panel; the article's revision moves; a retried upload makes no duplicate; another company's key and a reader without access get 404; revoking access stops the download; detaching from one article leaves the same document on another
- a server with
upload_max_filesize = 2Mandpost_max_size = 8M- the PHP defaults - takes a 30 MB document
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 ID, Company column and hover card β Developer Guide
- β³ π οΈ Task board and subtasks β Developer Guide
- β³ π§βπ€βπ§ People on a task ("Involved")
- β³ π Repeating tasks
- β³ π’ Moving a task between companies
- π Projects
-
Assets
- β³ π οΈ Asset list by type - review (#340)
- β³ π’ Moving an asset between companies
- β³ π Shared asset locations
- β³ π§βπΌ Assigning assets to analysts
- β³ π Warranty and lease alerts
- β³ π Leases
- β³ π Saved table views
- β³ π¨οΈ Recording anything, and importing it
- β³ π§© Asset type layouts
- β³ π Inventory freshness
- β³ π Linked configuration item
- β³ π Connected assets
- β³ π Asset review
- β³ π Missing information
- β³ π¦ Consumables
-
β³ π·οΈ 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)
- β³ π οΈ Back to your page after sign-in β Developer Guide
- β³ π Request catalogue
- β³ π Portal privacy
- β³ π₯ Portal managers
- β³ π Contact details
- β³ π οΈ Developer guide
- LMS
- Process Mapper
-
CMDB
- β³ π§± Designing your CMDB
- β³ π οΈ CMDB β Developer Guide
- β³ π οΈ Impact analysis β Developer Guide
- β³ π οΈ Data quality β Developer Guide
- β³ π οΈ Record references β Developer Guide
- β³ π οΈ CMDB assistant - Developer Guide
- β³ π Linked assets
- β³ π Linking an asset to its CI - design (#201)
- β³ π Discovery and redundancy-aware impact - design (#199)
- β³ π οΈ Relationship wording - review (#297)
- Network Mapper
-
Workflows
- β³ π Branches: If / Otherwise and Choose by value
- β³ π οΈ Workflow engine β Developer Guide
- β³ π οΈ Workflows for tasks β Developer Guide
- β³ π οΈ Workflow notes on a ticket β Developer Guide
- β³ π οΈ Workflow category routing β Developer Guide
- β³ π Workflows in order, child tickets - design (#304)
- β³ β° Time-Based Triggers
- β³ πͺ Webhooks
- β³ π¬ Webhook Message Formats
- β³ π HTTPS Certificates & CA Bundles
- β³ π οΈ SSL Verification β the Global Setting
- β³ π Workflow & Webhook Pitfalls
- Issue trackers (Jira, Azure DevOps)
- π‘ Zabbix (monitoring)
- π¬ Microsoft Teams alerts
- π 3CX (phone system)
-
System
- β³ π οΈ System cards by topic - review (#347)
- β³ π¦ Microsoft 365 (Entra ID and Intune)
- β³ π οΈ Preferences β Developer Guide
- β³ ποΈ Settings on one page
- β³ π§Ή Maintenance
- β³ πΎ Storage usage
- β³ βοΈ Emailed reports
- β³ π Finding people in the Analysts list
- β³ πͺ When an analyst leaves
- β³ π οΈ System β Branding β Developer Guide
- β³ π©Ί Page health (D019) β Developer Guide
- β³ β Feature Bingo
- β³ π Locations
- β³ π·οΈ Cost centres
- β³ π Chart of accounts
- β³ π· Photo Album
- β³ Demo Data
- β³ π οΈ Demo Data β Developer Guide
-
Overview
- β³ π Progress tracker
- β³ Concepts & vocabulary
- β³ Email routing & mailboxes
- β³ Settings: global vs per-company
- β³ Users & self-service
- β³ Staff cross-company access
- β³ One company supporting another
- β³ π’ One board across every company
- β³ Worked examples
- β³ Pitfalls & gotchas
- β³ Scope: what it's for
- β³ π οΈ Developer Guide (make a module multi-company)
- β³ ποΈ Case study: CMDB (a linked graph)
- β³ π§ͺ Test harness (prove it's isolated)
- What this is
-
π Bugs resolved
- β³ π #413 Reading pane too narrow on tablets
- β³ π± #412 Sign-in card cramped on phones
- β³ π§ #411 Header buttons out of reach
- β³ π± #386 Project stuck in an old currency
- β³ π₯οΈ #393 Header ran off the screen
- β³ π±οΈ #395 Ticket flyouts ran off the bottom
- β³ π PR #401 Change editor used hardcoded priorities
- β³ π Knowledge drafts could not be published
- β³ π§© #392 Project dialogs shared element ids
- β³ πΌοΈ #391 Knowledge images from your computer
- β³ π #375 REST API wall-clock times
- β³ π #374 Calendar popup ran off the screen
- β³ π’ #373 All companies: Changes, CMDB, Starters
- β³ π’ #356 Assets People and All companies
- β³ π #366 LMS demo data would not import
- β³ π #362/#365 Team handover showed only a name
- β³ π #365 The bell credited the wrong person
- β³ ποΈ #369 Inbox empty until Database Verification
- β³ πͺ #360 Links opened inside the ticket
- β³ π #354 Workspace Links missed tasks
- β³ π Task company checks in the API (5.5.0)
- β³ π Asset holders through the API (5.4.0)
- β³ π Files folder delete did not check inside (5.4.0)
- β³ π The Intune tab did not check the company
- β³ π #332 Files viewer would not open
- β³ π #333 Note attachments downloaded
- β³ πͺ #326/#327 Form webhook Full record
- β³ π #325 Form PDF download failed
- β³ π Small fixes in 5.1.0
- β³ π CMDB relationships read backwards (5.1.0)
- β³ π #301 CSAT delay was never applied
- β³ π #281 Comments imported from Jira never arrived
- β³ π #288 A change failed to open with Enforce approvals on
- β³ π Long non-Latin articles never got an embedding
- β³ π« #280 Email lookups scanned the whole table
- β³ β #266 Dragging a task told nobody
- β³ π #255 Article previews showed HTML codes
- β³ π #252 A link to a Knowledge article did not open
- β³ π #254 PDFs could not print Polish
- β³ π #250 Clicking a folder left the open article on screen
- β³ π« #260 The dashboard cog did nothing
- β³ π« #248 A department rule never matched on four routes
- β³ π A directory account could be matched to someone else
- β³ π« #244 Reply went to the assigned analyst
- β³ π Mailbox sign-in was not checked
- β³ π Four weaknesses around signing in
- β³ π A lookup answer could name any record
- β³ π« #227 A mailbox could not be deleted
- β³ π« #226 A picture on a note could not be closed
- β³ π» #222 The Assets page never loaded in 4.3.0
- β³ βοΈ #214 A "contains" condition did not match capitals
- β³ βοΈ #216 A workflow email from a chosen mailbox always failed
- β³ π³ The Docker image was missing PHP extensions
- β³ π A failed DNS lookup read as a missing record
- β³ π A link could change data
- β³ π Access outlived its removal
- β³ π Knowledge articles could run scripts
- β³ π Knowledge writes ignored permissions
- β³ π Company boundaries (Oct 2026)
- β³ π Smaller gaps (Oct 2026)
- β³ π Escaped text could leave its attribute
- β³ π Task descriptions were not cleaned
- β³ π Task documents ignored company scope
- β³ π Repeating tasks ignored company scope
- β³ π¬ #183 Mailbox checks overlapped
- β³ π #188 Transfer lock shown off when unknown
- β³ β #184 Subtask names and Overdue
- β³ π§© #186 Teams: the buttons did nothing
- β³ π Text in a change could run script
- β³ π AI settings changed without the AI permission
- β³ πͺ #178 Deleting an analyst failed
- β³ π« A team with no departments showed 0 tickets
- β³ π Projects: adding a phase did nothing on Save
- β³ π Leavers could still sign in
- β³ πΌοΈ Logo and courses broke on Apache with PHP-FPM
- β³ π’ Chat tickets ignored your ticket numbering
- β³ π Dates shown as a dash, or in server time
- β³ π Assets β Users showed people from other companies
- β³ π Restricted analysts could read other modules' data
- β³ πΌοΈ Replies with a picture in the thread failed to send
- β³ π Reply attachments never reached the customer
- β³ π οΈ Outbound email attachments β Developer Guide
- β³ π A global SSO provider was missing from the portal
- β³ π Behind a proxy, the SSO redirect said http
- β³ βοΈ The portal tagline moved when you saved it
- β³ π¨ The portal settings screen forgot what you saved
- β³ π‘οΈ The approvals inbox said "Error" and nothing else
- β³ π A table's answers were missing from the PDF
- β³ β A single-select column let you tick every option
- β³ π The portal ignored a form's field widths
- β³ π The tasks board stopped taking clicks
- β³ ποΈ #121 The index list is out of date after upgrading
- β³ π #133 The calendar subscription was empty
- β³ π #131 Tasks always reopened on the board
- β³ π₯ #129 Every page returned HTTP 500 after upgrading
- β³ π³ #127 A PHP warning above the System page
- β³ π #126 Notes stamped with the server's clock
- β³ π Storing every date in UTC
- β³ πͺ The portal was down for everyone signed in
- β³ βοΈ #120 Workflow notes could never be written
- β³ βοΈ #123 Three errors when running Database Verification
- β³ π #122 The description box was a stub in the corner
- β³ π£ Demo data deleted real accounts
- β³ π #117 Sign-in redirected to the wrong address
- β³ π¨ #108 The priority dot was invisible
- β³ β±οΈ #116 Time logged from the right-click menu
- β³ π #114 API keys refused by our own guard
- β³ ποΈ #110 Assigning a task told nobody
- β³ πͺ #107 Signed out while still working
- β³ π #103 "Share with Requester" reached nobody
- β³ π #102 Search found nothing for hyphens
- β³ πͺ #101 Source code editor opened behind
- β³ βοΈ #88 Subtasks could not be ticked off
- β³ π» #84 Asset deep link selected nothing
- β³ π« #79 A new ticket arrived with no status
- β³ π§ #79 A ticket from email did not say so
- β³ π #78 Bell opened to nothing
- β³ π¬ #77 Mail only collected from Inbox
- β³ π #74 The default password could not be changed
- β³ π¦ #70 Renaming an impact level
- β³ π€ #67 App-only mailboxes could not send
- β³ π #45 Verify only ever worked for Microsoft
- β³ π #45 IMAP reported as not authenticated
- β³ βοΈ An email template stopped escaping itself
- β³ π The portal dashboard showed the wrong time
- β³ π’ The folder said 99 and the list showed 96