Issue #74: the default password could not be changed
Write-up of the reported fault and the three further instances found with it,
plus the Bugs-Resolved index row.
Issue #79 write-ups, Watchtower settings pair, browser extension dev guide
Six new pages and five updated.
New:
- Issue-79-Ticket-Status-Not-Set — the reported status fault. Seven
creation paths, the priority that survived because "Normal" is the same
word in German, and the header fallback that displayed "Open" BECAUSE
no status was stored.
- Issue-79-Ticket-Source-Not-Set — the other half of the same report.
Why it could not be a one-line fix (ticket_origins has no is_default
and is company-scoped), the per-mailbox dropdown that dissolved it, and
the dismissible health mark.
- Configurable-Lookups-Developer-Guide — the through-line. Thirty-plus
places across five modules, three of them wrong in English on a stock
install; what to read instead of a name; the two derivations; the
"don't borrow a domain fact for a view decision" rule; and the
whole-payload rename diff that proves a fix.
- Watchtower-Settings + Watchtower-Settings-Developer-Guide — the pair.
- Browser-Extension-Developer-Guide — the endpoint, the payload keys, and
the trap of being the second consumer of a shared payload.
Updated:
- Watchtower — was describing eight cards and metrics that no longer
exist; now ten, with the settings link.
- Browser-Extension — corrected the badge description, added the update
notice and the dev guide link.
- Mailbox-Authentication — the Default ticket origin and the ! mark,
including why warnings can be dismissed and errors cannot.
- Bugs-Resolved — three rows.
- _Sidebar — nested entries under Watchtower, Browser Extension and Bugs
resolved.
Both validations clean across all 190 pages: every [Link] resolves to a
real .md, and every backticked path exists in the repo. Seven bare
filenames were promoted to full paths, as on the Forms and Slack pairs.
Write-up for issue #77, and index it
A Microsoft 365 mailbox could only ever collect mail from Inbox. Covers why it
was never a regression (Graph accepts seven well-known folder names in a path
and treats everything else as an identifier, so reading a folder BY NAME had
never worked), why the screen contradicted itself (the move-to field had the
resolver and a Verify button, the read-from field had neither), what changed,
and what remains unproven -- a successful nested match, and the app-only
combination.
Adds the row to Bugs-Resolved and the sidebar entry.
Write-up for issue #78, and index it
The notification bell opened to nothing on the home page while working
everywhere else. Covers why the badge stayed correct (the count is fetched by a
function that touches no translations), why nothing was logged (the throw was
one line ABOVE the try, so the fetch never ran and the catch that would have
said "couldn't load" was never entered), and the two further pages that had the
identical fault and were fixed with it.
Adds the row to Bugs-Resolved and the sidebar entry.
Bugs Resolved index + write-up for issue #70
A landing page for resolved bug reports, linked from the sidebar, and the
first dedicated write-up under it: why renaming the Operational impact level
split the status board in two.
The #70 page covers the reported symptom, the reason healthy services were
the broken ones (their status is derived, not stored, so six places invented
the literal 'Operational'), the four further faces of the same bug that were
not reported, the fix via the is_default flag, a colour-keyed file table, and
how it was verified including the positive control.
The index also lists two closed bug reports that have no write-up yet, so the
gap is visible rather than forgotten.
Service-Status gains a paragraph on how a healthy service's status is derived,
linking to the write-up.