Repository navigation
War Room Message Actions Design
Asked for by Ed (21 Nov 2026) · Status: pieces 1 and 2 built (reactions, quote, copy, links, the viewer; pin, save, mark as unread) - the rest to come · The module today: War Room, War Room - Developer Guide
Right-click a message in the war room - or its ⋯ button, or a long-press on a phone - and a menu offers everything you would expect from a modern chat: react with an emoji, reply in a thread, quote, copy the text or a permanent link, forward, save, pin, mark as unread, translate, edit or delete, and see who has read it. The + button attaches a file from your Computer or from Files - a Files file is a live link that always opens the latest version and keeps to Files' permissions. Any attachment opens in the same draggable, resizable viewer as Files and Tickets.
War Room said: "Still deliberately absent: no threads, no emoji reactions, no message permalinks. These are polish on a tool people use all day; this is not that tool." On 21 Nov 2026 Ed asked for all three and more. The same page already argued the other way - "a tool nobody enjoys using in calm conditions is not the one they reach for at 3am" - and that is the argument that wins.
- Nothing on the page comes from the internet. Emojis are the Unicode characters your computer already draws; the full emoji list ships with FreeITSM as a file. The file viewer's libraries are the ones already bundled for Files. Translate is the one exception, like Warbot's plain-English mode and the situation report: it needs the AI provider, only shows when one is set, and the chat never waits for it.
- No permission stands between an analyst and the chat. Anyone who can post in a conversation can react, pin, thread, quote and forward in it.
-
Message text is never HTML. Everything is still inserted as text (
textContent); a quote or a forward is a structured reference drawn by the page, not pasted markup. - The poll stays idempotent. A reaction, a pin, a new thread reply or a read changes a message the reader already holds, so it must come back through the poll's "changed recently" path and the client must replace the message, never append (see Developer Guide §3).
Opened by right-click on a message, a ⋯ button that appears on hover (and is reachable by keyboard), or a long-press on a phone (phone styling only - the desktop is not touched).
- Ten quick reactions across the top: 👍 ❤️ 😂 😮 😢 🎉 👀 ✅ 🙏 🔥, then + for the full picker.
- Reply in thread · Quote · Copy message · Copy link · Forward to... · Save · Pin · Mark as unread · Translate · Seen by · Edit · Delete
- Items that do not apply are left out, not greyed: Edit only on your own messages, Delete on your own (or anybody's for an administrator, as today), Translate only when an AI provider is set, Seen by only when it is switched on.
| Action | How it works |
|---|---|
| React | Click an emoji to add your reaction; click it again (in the menu, or the reaction under the message) to take it away. Under the message: each emoji with its count; hover to see who. The full picker has categories, a search box (English emoji names - 1,800+ names are not translated; the category names are), and your recently used ones first. One reaction per emoji per person. |
| Reply in thread | Opens the thread in a side panel. The channel shows "3 replies · last 2 min ago" under the message, and nothing else, so the conversation is not cluttered. An Also send to channel tick posts the reply in both. Mentions in a thread notify as usual. |
| Quote | Your reply shows the original in a quote box above it - author, time, the start of the text - and clicking it jumps to the original. It is a reference, not pasted text: if the original is deleted the box says so. |
| Copy message | Copies the text, with the author and time, as plain text and as formatted text. |
| Copy link | A permanent link by database id - war-room/?channel=12&message=3456. Opening it shows the conversation scrolled to that message and highlights it, loading older messages if needed. Someone who cannot read the channel gets "not available"; a message removed by retention says so. |
| Forward to... | Pick a channel or a person you can post to. The forward says where it came from (Forwarded from #network, Sarah Williams, 10:42) and links back - the link only works for people who can read the original. A file uploaded from the computer is copied with it (war room files never change, so a copy always matches, and deleting a message still really destroys its file). A Files card is forwarded as the same link, never a copy. |
| Save | Your own bookmark. A Saved list in the left panel opens each one in place. Nobody else sees it. |
| Pin | Pinned for everyone in the conversation: a bar at the top - "📌 3 pinned" - opens the list, each with who pinned it and when. Anyone in the conversation can pin and unpin; who did is shown. |
| Mark as unread | Moves your "read up to here" marker back to just before this message, so the channel shows as unread until you come back to it. The page stops marking that channel read until you open it again. |
| Translate | The translation appears under the message, for you only, in your FreeITSM language, using the War room → Settings AI provider. Translations are kept, so asking again costs nothing. |
| Seen by | Who has read the message and when. Worked out from each person's read marker, with the time their marker first passed the message recorded as it moves, so "read at" is real. On by default; War room → Settings can switch it off for the whole install (some teams find read receipts intrusive). Mark as unread does not change when you first read it. |
| Edit / Delete | As today: your own messages; administrators can delete anybody's; both leave a visible mark. They move into the menu. |
The + button offers two choices:
- Computer - uploads the file into the chat, as today.
- Files - opens the Files picker (the one Tickets uses for From Files). The message gets a card, not an attachment: an icon for the file's type (Word, Excel, PDF, image, ...), its name, its size, and a small from Files mark so people know it is a live link. Icons are drawn by FreeITSM itself.
A Files card:
- Opens the latest version - if somebody edits the document tomorrow, everyone who clicks the card sees the new version.
- Keeps to Files' permissions, for the person clicking - not the person who shared it. Download permission: the file. View only: a view, no download, and the folder's watermark if it has one. No access: the card still shows the file's name (it was posted into a chat they can read, and the name lets them ask), with "You don't have access to this file in Files."
- Deleted or in the bin: "No longer available in Files"; restored from the bin, it works again.
Clicking an attachment - from the computer or from Files - opens it in the shared viewer (FilesViewer, assets/js/files-viewer.js), the draggable, resizable window Files and Tickets use: PDF, Word, Excel, images, video, audio, text, and zips browsed like a folder.
- A file uploaded from the computer opens with
FilesViewer.openUrl(), as a ticket's email attachment does, with Download beside it. - A Files card opens with
FilesViewer.openItem(), as a file linked from Files in a ticket does - so view-only and watermarks apply. - Types the viewer cannot show still simply download.
Each piece ships on its own.
- ✅ The menu, reactions (quick and full picker), quote, copy message, copy link and opening a link; attachments open in the viewer. Built 21 Nov 2026 - see Developer Guide §7a. Edit and Delete stay on the message as well as in the menu. Copy message copies plain text (messages have no formatting).
- ✅ Pin, save, mark as unread. Built 21 Nov 2026. Saved is a button beside Search rather than in the left panel - it lists across conversations, like Search does. Pins capped at 50 per conversation.
- Threads.
- Forward, Seen by (with its setting).
- Translate.
- Attach from Files - the cards.
| New | For |
|---|---|
warroom_reactions (message, analyst, emoji; one row per emoji per person) |
reactions |
warroom_pins (channel, message, pinned by, when) |
pins |
warroom_saved (analyst, message, when) |
Saved |
warroom_read_marks (analyst, channel, up to message, when) - one row each time a read marker moves forward |
Seen by's "read at" |
warroom_translations (message, language, text) |
translations kept |
warroom_messages.thread_root_id, .quote_of_id, .forwarded_from_id, .changed_datetime
|
threads, quotes, forwards; changed_datetime is what makes a reaction, pin or thread reply come back through the poll |
warroom_file_links (message, Files item) |
Files cards |
All of them go with their message (foreign keys that cascade), so retention and delete keep working as they do. Detail is settled in each piece's own developer guide.
| Date | Decision |
|---|---|
| 21 Nov 2026 | Build the message menu with every action above - reversing "no threads, no emoji reactions, no message permalinks" (Ed). |
| 21 Nov 2026 | Seen by on by default, with a War room → Settings switch to turn it off (Ed). |
| 21 Nov 2026 | Anyone in the conversation can pin and unpin; who did is shown (Ed). |
| 21 Nov 2026 | Thread replies stay in the thread, with an Also send to channel tick (Ed). |
| 21 Nov 2026 | Forwarding copies a computer attachment - war room files never change, so the copy always matches, and deleting a message still really destroys its file (Ed, after weighing a shared link). |
| 21 Nov 2026 | + offers Computer or Files. A Files file is a live link shown as a card with a type icon: latest version, the viewer's own Files permissions, its name shown even to people without access (Ed). Forwarding forwards the link. |
| 21 Nov 2026 | Every attachment opens in the shared viewer used by Files and Tickets (Ed). |
| 21 Nov 2026 | Copy offers a choice: just the text, or with the name and time (Ed) - built as two menu items rather than a hover submenu, which works the same by keyboard and on a phone. |
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
- ↳ 📋 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