Skip to content

War Room Message Actions Design

Ed Mozley edited this page Nov 21, 2026 · 3 revisions

💬 War room: doing things with a message - 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

In one paragraph

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.

This reverses an earlier decision

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.

Rules that do not change

  • 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).

The menu

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.

Each action

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.

Attaching: Computer or Files

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.

Opening any file

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.

Built in this order

Each piece ships on its own.

  1. ✅ 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).
  2. ✅ 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.
  3. Threads.
  4. Forward, Seen by (with its setting).
  5. Translate.
  6. Attach from Files - the cards.

Data (sketch)

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.

Decided

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

Getting Started

Modules

Multi-tenancy (planned)

Responses to feedback

Blue sky thinking

Bugs resolved

Pull requests

Links

Clone this wiki locally