Bugs Resolved

Bugs resolved

Bugs that have been reported, understood and fixed — each one written up so you can see what was actually wrong rather than just that something changed.

Every write-up covers the same ground: what you saw, what was broken underneath, how it was fixed, which files changed, and how the fix was proved. They are written to be read by somebody who has hit the same symptom, so the plain-English half comes first and the code comes after.

Found something? Please open an issue. A report with the steps to reproduce it is worth a great deal — several of the entries below were diagnosed correctly by the person who reported them.

---

Resolved

Reported	What was wrong	Module(s)	Issue	Resolution
Aug 2026	A folder in the ticket inbox showed a count that the list underneath did not match — All Tickets read 99 and listed 96 — and the missing tickets could not be reached by any route at all, not even by ticket number. Two unrelated causes: tickets that had been merged away were still counted, and the list was built starting from email messages rather than from tickets, so a ticket with no email against it was counted everywhere, listed nowhere, and impossible to open	Tickets	found while building #73	The folder said 99 and the list showed 96
Aug 2026	A brand-new installation could not get past its own first screen: FreeITSM insists the seeded password is replaced before anything else, and on that page the button did nothing while the console filled with 404. The page asked for its endpoint without naming the application root, so the address only resolved at one of the two addresses the page answers on — and the fix to #68 had just changed the application to send people to the other one. Four pages had it, including the one-time-code step of sign-in, which meant nobody with two-factor authentication could sign in at all	System · Authentication	#74	The default password could not be changed
Aug 2026	A ticket created from the mail inbox had no status at all — blank in the list, empty in the dropdown — on an installation that had renamed Open. Seven creation paths asked for the status by name, and the reading pane went on displaying Open anyway, so the header and the list disagreed and neither looked wrong	Tickets · Portal · Web chat · Workflows	#79	A new ticket arrived with no status
Aug 2026	Tickets collected from email did not record that they came from email — the Source field was blank on every one, so no report could tell them from any other kind	Tickets · Mailboxes	#79	A ticket from email did not say it came from email
Aug 2026	Watchtower counted by typed-in words, and three of them were already wrong in English on a stock installation — the open-ticket headline read 88 against a true 100, Morning Checks reported "all checks completed and passing" on a morning when every check was red, and completed changes were counted as upcoming work	Watchtower · Browser extension	found while fixing #79	Never identify a lookup row by its name
Aug 2026	A Microsoft 365 mailbox could only ever collect mail from Inbox — any folder of your own gave 400 ErrorInvalidIdMalformed and collected nothing, while the Verify button beside the field below happily confirmed the very same folder	Tickets · Mailboxes	#77	Mail could only ever be collected from Inbox
Aug 2026	The notification bell showed a correct red count and opened to an empty panel on the home page, while working everywhere else — it was never sending the request, and the error handler sat one line below the failure so nothing was reported	Notifications · System · Problem Management	#78	The notification bell opened to nothing
Aug 2026	Renaming the Operational impact level split the status board in two — services in an incident showed the new name, healthy ones kept the old one and lost their badge colour	Service Status · Self-Service Portal · Watchtower · REST API	#70	Renaming an impact level
Aug 2026	login.php was missing — a rewrite rule had been hiding around ninety wrong paths, so installations without one (nginx, or Apache with AllowOverride None) could not sign in	Core · Installation	#68	Root folder tidy · Running on nginx
Aug 2026	Mailboxes set to app-only authentication could receive email but never send any — every outgoing route addressed the message to "the signed-in user's mailbox", which does not exist in app-only mode	Tickets · Workflows · Self-Service Portal	#67	Why app-only mailboxes could not send email

---

Closed, but not yet written up

These were reported and fixed before this page existed, and deserve the same treatment. Listed here so the gap is visible rather than quietly forgotten.

What was wrong	Issue
API keys generated in the interface were not stored in the apikeys table	#65
Priorities were missing on ticket creation	#40

---

What counts as a bug here

This page is for things that were broken, not for things that were missing. Suggestions, feature requests and new modules are tracked separately:

• Features and improvements as they ship — freeitsm.co.uk/updates.php
• Ideas being considered — Blue sky thinking
• Everything else — the GitHub issues list

A few recurring themes are worth knowing about in their own right, because they are the sort of thing that bites more than once:

• Workflow & webhook pitfalls — the failures that look like nothing happening
• Database integrity — foreign keys and constraints, and what happens without them
• Mailbox authentication — the troubleshooting table for email that will not send or collect