OpenSparrow Files

Added

• [Record: table:id] links in comments — a comment body can now reference another record by writing [Record: table:id], and it renders as a clickable link that opens that record. A record picker dialog (public/assets/js/comments.js) inserts the marker automatically, so users never hand-type ids; the markers are extracted server-side by includes/comment_links.php and validated against the schema before being trusted. Link markers are translated-agnostic (table + numeric id) and drop safely to plain text where a record no longer exists.

• @mentions in comments with in-app notifications — typing @username in a comment (with an autocomplete picker, public/assets/js/comments/mention.js) mentions an active user and delivers an in-app notification. The mention is parsed by includes/comment_mentions.php, matched against spw_users (active, non-author accounts), and written into spw_users_notifications with a title ("X mentioned you") and a deep link to the record's Comments tab; the insert is idempotent (ON CONFLICT … DO NOTHING), so repeated mentions on the same record/comment do not spam.

• User info tooltips on comment authors and record owners — hovering a comment author or a record owner now shows a tooltip with the user's full name, role, email and phone, fetched by includes/user_info.php and rendered through the shared enableUserTooltips() funnel (public/assets/js/util/user-tooltip.js). The same helper also upgrades existing data-username anchors, so @mention chips and comment author links all get the info tooltip for free.

• Shared ? help cursor on every tooltip — all record and user tooltips are now funnelled through showRecordTooltip() / enableUserTooltips(), which apply the os-tip class and a cursor: help affordance, so every tooltip target shows the question-mark cursor consistently (grid cells, board cards, calendar chips, roadmap bars, drilldown rows, owners, comment authors). A hand-rolled cursor on the grid cell was removed in favour of the single shared rule.

Changed

• Unified frontend button, font and table styling — buttons now inherit the page font everywhere (a plain <button> no longer falls back to Arial), and the primary/secondary/destructive button classes were collapsed onto the shared .btn-save / .btn / .btn-delete catalogue with one visual recipe. Design tokens (--accent, --bg, --border, --radius, --shadow-*, --font-sans/--font-mono) are now the documented source of truth in public/assets/css/styles.css, and the edit/create forms render Excel-style subtable borders, gray headers and zebra rows using the same shared recipe as the record tables.

• Grid row actions column moved first — the row-actions column (edit/delete) now renders as the leftmost column of the grid instead of the last, so the action buttons sit next to the record's identity regardless of how many columns are hidden.

• Setup wizard simplified — the database step no longer prefills the database name, user or password (or a default schema); only the host (localhost) and port (5432) are prefilled, so a fresh install cannot accidentally target placeholder credentials. The config/demo_meta.json install marker is now documented.

• Demo CRM phone masked for viewers — the demo CRM's contact.phone column now carries the mask_for_viewer flag, so a read-only Viewer sees ••••• in place of the seeded phone numbers while editors and admins keep the real values.

Fixed

• Comment tooltip and record-link edge cases — record markers with a non-positive id are rejected before being turned into links, and mention/notification failures log to error_log without leaking driver text into the client.

Upgrade notes

• No database migration is required and no configuration keys are removed by this release. All features live in the existing spw_comments, spw_users and spw_users_notifications tables and in the schema/spw_config configuration.
• Mentions and record links are opt-in by usage — no toggle, nothing to enable. Mentions only notify active, existing, non-author accounts, and the notification cron (which already delivers note reminders) surfaces the new in-app items; no new cron wiring is needed.
• The tooltip cursor and font/button unifications are presentation-only — they change how the frontend looks and behave, not the API, the database or the access model. Nothing to migrate.

Full changelog: https://github.com/wrobeltomasz/OpenSparrow/compare/4.2...4.3