Repository navigation
Asset Label Designer Design
Status: slices 1 and 2 are built (4.8.0) - label designs, sizes, fonts, the exact-size PDF, and the designer; barcodes (slice 3) are next. Two things in section 2 were left out of the designer for now: a Print preview button (the label is already drawn as it prints, with a real asset) and a label background. For users: QR asset labels - Label designs and The label designer; for developers: QR asset labels - Developer Guide Β§6b and Β§6c. This page sets out how I plan to build issue #229, raised by @zemega. It is written before the code so the approach can be checked first. The open questions are in section 11.
The request, from the issue:
"The rigid layouts do not align properly with continuous-tape label makers, such as Brother TZe tape printers ... Logos cannot be displayed prominently, which is a key requirement for internal stakeholder and management satisfaction."
Today every asset label has the same shape: the QR code, the asset tag and a list of fields, with the logo squeezed into the middle of the QR. It prints on four sizes of A4 sheet and nothing else.
This design adds a label designer, built to feel like the Report Pack designer - a ribbon, a toolbox, the label in the middle with rulers, and a properties pane - where you place things anywhere on the label, the way you place shapes in PowerPoint:
- Any size of label. A 24 mm Brother tape, a 62 mm Dymo label, the A4 sheets you use today, or your own size.
- Anything, anywhere. Your logo at any size, the QR code, any asset field, your own text, lines and boxes. Drag them, resize them, line them up.
- Printed at exactly its size. A PDF the size of one label, one label per page for a tape printer, or laid out on a sheet - so the printer's driver gets exactly what it expects.
- More than one design. "Laptop tape label", "Server sheet label" - each company keeps its own, with one as the default.
Nothing changes until you choose to. Today's layout becomes the first design, so labels print as they do now until somebody opens the designer.
From QR asset labels and its developer guide:
| Today | |
|---|---|
| Layout | One fixed shape: an optional header, the QR, the asset tag, an ordered list of fields, an optional footer. Built with CSS; font sizes worked out from the label's height |
| Configured |
Assets β Settings β Asset labels & QR (Cap::ASSETS_LABELS): which fields and in what order, header, footer, field names on or off, and a logo. Six settings, per company (tenant_settings, falling back to system_settings) |
| Fields | Asset tag (always, first), hostname, serial, manufacturer, model, company, location, type, and custom fields as cf_<key>
|
| Logo | In the middle of the QR, at about 22%, which switches the code to error correction H. Small by design |
| Codes | QR only, drawn in the browser by the bundled qrcode.min.js. It encodes /a/<qr_token>
|
| Printing | Four A4 sheets (65, 40, 24 or 12 per sheet), through the browser's print dialog. No tape printers, no other sizes, no PDF |
| Also | A CSV for a professional print house |
When labels were last reviewed (PR #164), a full designer was set aside: "physical dimensions, browser print scaling and long values make a designer a project of its own. Nobody has asked for one." This design takes each of those three on directly: exact physical sizes (section 4), a PDF instead of browser printing (section 6), and rules for long values (section 3).
It is built to feel like the Report Pack designer, from the same patterns (Report Packs internals 1), so the two read as one product:
- A fixed application frame: title bar (name, Saved / Unsaved, undo, redo, Save, Print preview), a ribbon, the toolbox on the left, the label in the middle, the properties pane on the right, a status bar. The page never scrolls; the panes do.
- The ribbon: Home (clipboard, undo, delete), Insert (text, field, QR code, logo or picture, line, box - and barcode, section 9), Arrange (align left / centre / right / top / middle / bottom, distribute, bring forward, send back, rotate), Label (size and stock, background, preview with an asset).
- The label is drawn large on a pasteboard, with rulers in millimetres, zoom (Ctrl+wheel, Fit), a grid you can switch on, and snapping to the grid, the label's edges and centre lines, and other items' edges and centres - with the pink guide lines PowerPoint shows while you drag.
- Selection with handles to resize, Shift to keep proportions, marquee select, Shift-click to add, arrow keys to nudge (Shift for larger steps), Ctrl+D duplicate, Ctrl+C / V across designs, Delete, right-click menu. Undo and redo for everything.
- The properties pane shows exactly what the selected item can do - position and size in mm, font, size, bold, alignment, how long text is handled, the field it shows, the QR's options.
- Preview with a real asset: pick an asset (or "the longest names") and the label shows its real values, so you see whether a long model name fits before printing 200 of them.
What is different from Report Packs: a report flows down pages in rows of blocks; a label is small and every item has an exact position. So the canvas works like the free placement in the Process and Network Mappers, not like Report Packs' rows.
Every item has a position and size in millimetres (to 0.1 mm), and a rotation of 0, 90, 180 or 270 degrees - tape labels often want a column of text turned on its side.
| Item | What it shows | Options |
|---|---|---|
| Text | Your own words - "Property of ZHL Group", "IT helpdesk ext. 4000" | Font, size, bold / italic, alignment, colour (black or white on a filled box) |
| Field | One asset value: tag, hostname, serial, manufacturer, model, type, company, location, holder, a custom field | Its caption on or off ("Serial: ..."), plus Text's options. Text can also hold fields inline: S/N {serial}
|
| QR code | The asset's code - the same /a/<qr_token> as today, so labels already printed keep working |
Logo in the middle on or off (today's look), quiet zone |
| Logo / picture | The company logo, or any picture uploaded to the design | Keep proportions; black-and-white conversion for thermal printers |
| Line, Box | Separators and frames | Thickness, filled or not |
| Barcode | A 1D barcode of the tag or serial, for hand scanners that read only barcodes | Section 9 - a later slice |
Long values - the third worry from PR #164. A field's box is a fixed size, so each field says what happens when its value does not fit: shrink to fit (down to a smallest size you set, default), wrap onto more lines, or cut off with "...". Nothing is ever printed outside its box or over another item. The preview's "longest names" asset shows the worst case.
A design says what one label looks like. The stock says how labels come off the printer. A design is drawn for one label size; the stock is chosen when the design is made, and can be changed.
| Stock | What it means | Examples (presets) |
|---|---|---|
| Tape or roll | One label per page, the page exactly the label's size | Brother TZe 12, 18, 24, 36 mm; Brother DK 29 x 90, 62 x 29; Dymo 89 x 36, 54 x 25; your own width and length |
| Sheet | Labels laid out in rows and columns on a page, with margins and gaps | Today's four A4 sheets, common Avery / Herma sheets, your own |
A tape label's length is part of the design - a 24 mm tape can be 50 mm or 90 mm long. For sheets, a printer offset (a millimetre or two left / down) can be saved, because "check the alignment on plain paper first" is the advice today and an offset is how you act on it.
A new table, asset_label_designs:
| Column | |
|---|---|
id, name
|
"Laptop tape label" |
tenant_id |
The company it belongs to; NULL = every company (only somebody who reaches every company can make one) |
stock_json |
The stock: tape (width, length) or sheet (page, rows, columns, pitch, margins, offset) |
design_json |
The items, as one JSON document - like Report Packs' design, checked and cleaned by the server on every save |
is_default |
The design Print label uses unless you pick another; one per company |
version, updated_by, updated_datetime
|
Saving uses the version, so two people editing one design cannot silently overwrite each other (Report Packs' 409 rule) |
Uploaded pictures are stored with the existing upload rules (uploadStoreFile(), images only, size-limited), as the logo is today.
Who can do what. Designing labels stays under the existing Asset labels permission (Cap::ASSETS_LABELS) - it is the same job. Printing stays with whoever can print labels today.
Printing a label. Print label and the batch Print labels use the company's default design, with a drop-down to pick another. The CSV for a print house is unchanged.
Browser printing is what makes custom sizes unreliable: the browser adds margins, scales to fit, and picks the paper itself. A tape printer's driver expects a page exactly the size of the label. So printing becomes a PDF, made in the browser by jsPDF (already bundled for Report Packs), at the stock's exact size:
- Tape: one page per label, each page the label's size. Printed through the label printer's own driver at actual size.
- Sheet: pages of the sheet's size, labels placed at the sheet's pitch and offset.
The same drawing code draws the designer's canvas and the PDF, from one list of positioned items in millimetres - the Report Packs approach, which is why its screen and its PDF match. Nothing is sent outside the install: the QR codes and the PDF are made in the browser, as the codes are today.
Report Packs use the three standard PDF fonts, which hold drawings only for Western European characters - a Chinese or Arabic name prints as "?". On a label every character must print (decided on review). Two things are needed for that, and the design does both:
- A font that has the characters. Unicode numbers every character; a font holds drawings for some of them, and no single font holds them all. FreeITSM bundles one free font, Noto Sans (Latin, Cyrillic, Greek, Vietnamese), and you can upload your own (section 6a) - one for Chinese, Arabic or Hindi names, or your company's brand font.
- Something that lays the text out correctly. Arabic letters join; Hindi, Bengali, Tamil and the other Indic scripts combine letters. jsPDF does not do that; the browser does. So text is drawn by the browser, exactly as the designer shows it, and placed in the PDF as an image at 600 dots per inch - twice what most label printers print. The QR code, lines and boxes stay vector. What prints is exactly what the designer showed, in any language and any font.
Each text item can also name a fallback font: a character the chosen font lacks is drawn from the fallback rather than missed, so a brand font for English and a Noto font for Chinese can share one label.
The first real print (#229, a Brother D610BT on silver tape, the PDF printed from Firefox) showed the QR code sharp, the values readable, the field captions unreadable and the logo speckled. Cause: the captions were drawn at 55% of the field size in grey #444444, and the logo was dark grey. A thermal printer has no grey, so its driver halftones it into dots.
-
Captions, universal: the item's own colour, 70% of the value's size, never below 5 pt (or the value's size, if smaller).
linesFor()inrender.js. -
mono, per design, indesign_json: text, lines and boxes are drawn black, and the logo goes throughmonoImage()- enlarged to 1200 px, laid on white, black where darker than 160/255, clear elsewhere. Preview and PDF both honour it. Unset follows the stock (assetLabelMono()in PHP,monoFor()in JS): tape and roll on, sheets off - so every design made before 4.9.0 on a tape got the fix without anyone touching it. The settings modal only sendsmonoonce the box has been touched;save_itemskeeps whatever was there. - Considered and dropped: removing the soft edges from the 600 dpi text. The PDF is resampled before the printer sees it - Firefox's pdf.js prints at 150 dpi, then the driver resamples again - so grey edges come back whatever the PDF holds. The real lever there is the viewer: the user wiki says to print from a desktop reader or Chrome.
- Asked for, not built: one long strip of labels for chain printing, so a printer like the D610BT does not waste its fixed margin on every label. Waiting on how the reporter's driver handles a long custom page.
Under the designer's Fonts list, somebody with the Asset labels permission uploads a font file - .ttf, .otf, .woff or .woff2, up to 20 MB (a full Chinese font is about 15). It is checked to be a real font (its header and tables are read, and anything else is refused), stored with the existing upload rules, and offered in every design for that company. The designer and the PDF both load it with the browser's own font loading, so it looks identical in both.
- Licences. Some commercial fonts may not be embedded in documents. The upload screen says so, and the person uploading confirms they may use it. Noto Sans is under the SIL Open Font License, which allows this.
- Deleting a font in use by a design is refused, naming the designs, so no label silently changes its look.
- Database Verification creates the table. The first time labels are printed or the designer is opened, each company's current settings - fields, order, header, footer, field names, logo - become a design called "Standard" on today's sheet sizes, drawn to look as today's label does. It is that company's default.
- The six settings stay readable for one release, then the settings tab points to the designer (decided). Nothing the tab does today is lost - each part has its place:
| Today's tab | In the designer |
|---|---|
| Which fields, and their order | Field items, placed anywhere |
Custom fields (cf_<key>) |
The same, in the field list |
| Header and footer | Text items |
| Field names on or off | A caption option on each field |
| Logo upload (branding rules, 2 MB) | The logo item, same upload rules |
| Logo in the middle of the QR, error correction H | An option on the QR item, with the same rule |
| Asset tag always printed; "no tag" when blank | Kept in the Standard design, same wording |
| Live preview | Preview with a real asset |
Per company (tenant_settings, then system_settings) |
Designs per company, and designs for every company |
| The four A4 sheets | Sheet presets, same pitches and QR sizes |
| CSV for a print house | Unchanged, on the print screen |
- The scan side does not change at all: the QR encodes the same address, and every label already on a laptop keeps working.
So nobody starts from a blank label:
- Standard - today's layout (made from your settings, section 7).
- Tape, logo left - the layout in the issue: logo on the left, title and three fields in the middle, QR on the right, on 24 mm tape.
- Tape, small - QR and tag only, for 12 mm tape and small kit.
- Sheet, large - for 63.5 x 72 mm labels: logo across the top, QR, several fields.
Each slice is useful on its own, and comes with its tests and write-up.
- Designs, sizes and printing - the table, the stock presets (tape and sheet), the PDF printer with browser-drawn text, Noto Sans and uploaded fonts, today's layout as "Standard", the ready-made designs including logo left, QR right on 24 mm tape, and the design picker on Print label. This alone answers the issue's minimum request (the logo separate from the QR, prominent), and gets tape printers working.
- The designer - the ribbon, canvas, rulers, snapping and guides, properties, undo, preview with a real asset, as section 2 describes.
- More to place - 1D barcodes (Code 128, which every hand scanner reads; drawn by a small generator written for FreeITSM, as nothing in the install draws barcodes yet), and Data Matrix if anybody asks for it.
- Printing straight to a label printer over the network (Brother's and Zebra's own languages, ZPL / ESC-P). The PDF goes through the printer's normal driver, which every label printer has. A direct route can follow if the PDF is not enough.
- A design per asset type chosen automatically. You pick the design when printing; a default per type can come later.
- Editing the QR's contents. It stays the asset's own address, so a label can never point somewhere else.
For @zemega:
- How do you print to the Brother? From a PDF through the Windows / macOS Brother driver (my assumption), or through P-touch Editor, or something else? And which models and tape widths?
- Do you need a 1D barcode on the label, or is the QR enough? (Your settings screenshot had 1D Barcode unticked.)
- Rotation: on your 24 mm tape, is the label read along the tape (as in your screenshot), or do you also print labels turned across it?
Decided on review (2 November 2026):
- Fonts: every character must print. A free Unicode font is bundled, fonts can be uploaded, and text is laid out by the browser so every script is drawn correctly (section 6, 6a).
- The old settings tab points to the designer after one release, and nothing it does is lost (section 7).
- QR asset labels and its developer guide
- Report Packs and the designer's internals - the look and feel this follows
- Asset reconciliation, tags and labels - PR #164 review - where a designer was first discussed
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
- 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
- β³ π₯ Importing people from a directory
- β³ π₯ Importing people from Microsoft Entra ID
- β³ π³ OpenLDAP & Samba AD (Docker) setup
- β³ π οΈ LDAP β Developer Guide
- β³ π οΈ Directory sync β Developer Guide
- β³ π§© Extending directory sync
- β³ π οΈ Entra directory sync β Developer Guide
- β³ π₯ Directory sync β design
- π 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)
- β³ π οΈ Microsoft Entra ID import - review (#235)
- β³ π οΈ Assets from their Intune primary user - review (#236)
- β³ π οΈ Organisation chart - review (#242)
- β³ π« 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: Analysts
- β³ πΊοΈ REST API: Network Mapper
- β³ π§ Using the API docs page
- β³ π OpenAPI specification
- β³ β OpenAPI: kept correct
- β³ π οΈ Maintaining the catalogue
- Watchtower
-
Tickets
- β³ π οΈ 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
- β³ π 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
- β³ Mailbox Authentication
- β³ π€ Email send log
- β³ π Attachment size limits and large emails
- β³ Basic IMAP mailboxes
- β³ 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
- π 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
- Network Mapper
- Workflows
- Issue trackers (Jira, Azure DevOps)
- π‘ Zabbix (monitoring)
- π¬ Microsoft Teams alerts
- π 3CX (phone system)
-
System
- β³ π οΈ Preferences β Developer Guide
- β³ π Finding people in the Analysts list
- β³ πͺ When an analyst leaves
- β³ π οΈ System β Branding β Developer Guide
- β³ π©Ί Page health (D019) β Developer Guide
- β³ β Feature Bingo
- β³ π·οΈ Cost centres
- β³ π· 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 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
- β³ π A directory account could be matched to someone else
- β³ π« #244 Reply went to the assigned analyst
- β³ π 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