2026-11-19 00:37:39 -05:00
..
2026-11-18 18:27:03 -05:00
2026-11-17 19:24:04 -05:00
2026-11-18 01:52:00 -05:00
Module switches: Dispatch, Bookkeeping, Purchasing, Trips and Calendar can be switched off in Admin > Settings > Modules, Dispatch coming with ticketing and the other three with invoicing, each hidden from menus, dashboard, search, reports and the API and refused on its pages, windows and handlers while off; Purchasing starts off unless already in use, Bookkeeping off posts the default accounts in place of account pickers, database 3.9.4, new moduleOn, moduleOffText and bookkeepingAccount helpers, purchase order settings tile summary, 26.11.9 changelog entries
2026-11-18 14:27:16 -05:00
Knowledge Base stage 2: who can read each article - agents only, clients (all, by client tag or by name) or anyone - database 3.9.6 with kb_article_visibility, kb_article_all_clients, kb_article_client_tags, kb_article_clients and config_kb_public_enable, Help in the client portal with search, categories, print and Ask us, the public help center at guest/kb.php with its switch in Admin > Settings > Knowledge Base and a link on the sign-in page, a Who can read it column, filter and article panel, tag merge moving article client tags, tagKinds only listing kb_article once its table exists, and changelog entries
2026-11-18 17:36:51 -05:00
Leads: clients marked as leads are left out of the client pickers in record windows, bulk edits, Dispatch, the client switcher, the transaction filter and export, report pickers and coverage, template reports and use windows, agent banners, portal announcements, RMM client linking and managed instances, keeping the record's own client and the lead whose page it is; quote pickers keep leads after the clients marked Lead, global search lists them after matching clients marked Lead, new clientNotLeadSql helper, 26.11.9 changelog entries
2026-11-18 12:21:25 -05:00
AI stage 4: Billing use case falling back to General; Write it with AI on quotes and invoices whose lines can still change - say what it is for and AI picks lines from the product catalog at catalog prices and frequency, labor in quarter hours at the client's rate, and anything else unpriced for the agent to set (AI never sets a price), with a suggested scope, client note and pre-send checks, optionally using the quote's ticket and the client's people, sites and devices (ticket and documentation only with Support); ticked lines added through billing_ai_lines, taxed by kind, scope and note kept on request, lines that can't go on listed; Write it on the ticket Invoice window describes the work done from replies and notes for the client under the usual ticket line, passwords never sent nor written back; new functions/ai_billing.php, ai_billing_draft and ai_ticket_invoice_description endpoints, billing_ai_writer modal, billing_draft and invoice_description features; callAiApi remove mode also strips made-up secret placeholders; changelog
2026-10-20 21:23:52 -04:00
AI stage 4: Billing use case falling back to General; Write it with AI on quotes and invoices whose lines can still change - say what it is for and AI picks lines from the product catalog at catalog prices and frequency, labor in quarter hours at the client's rate, and anything else unpriced for the agent to set (AI never sets a price), with a suggested scope, client note and pre-send checks, optionally using the quote's ticket and the client's people, sites and devices (ticket and documentation only with Support); ticked lines added through billing_ai_lines, taxed by kind, scope and note kept on request, lines that can't go on listed; Write it on the ticket Invoice window describes the work done from replies and notes for the client under the usual ticket line, passwords never sent nor written back; new functions/ai_billing.php, ai_billing_draft and ai_ticket_invoice_description endpoints, billing_ai_writer modal, billing_draft and invoice_description features; callAiApi remove mode also strips made-up secret placeholders; changelog
2026-10-20 21:23:52 -04:00
AI stage 1: rebuild AI Providers and AI Models in the standard list pattern with ready-made provider kinds (OpenAI, Anthropic, Azure OpenAI, Gemini, Mistral, Groq, OpenRouter, Ollama, LM Studio, OpenAI-compatible), Test that lists a provider's models, Save anyway for a provider that doesn't answer, a first model offered when adding the first provider, the API key no longer shown, from-to audit lines, and delete confirms that say what goes and what stops; model window with suggested models, use case notes and Try it; new AI Usage page logging each request by feature, user, client, model, tokens, time and failure, with totals, views and filters, pruned with the audit log; passwords, keys, 2FA links and card numbers taken out before sending and put back in the answer, on by default per provider; new Use AI role permission; Reword shown only when set up and allowed, placed first in the toolbar, with its own instructions, undo in one step and a fixed endpoint on admin pages; ticket summary and template drafts purified; Settings overview warns while AI requests keep failing; database 3.3.8 adds provider kind and redact, ai_usage and module_ai
2026-10-20 17:45:00 -04:00
2026-11-16 18:17:49 -05:00
2026-11-18 01:52:00 -05:00
2026-11-18 01:52:00 -05:00
2026-11-17 19:22:47 -05:00
2026-11-18 01:52:00 -05:00
2026-11-09 01:22:35 -05:00
2026-11-18 01:52:00 -05:00
2026-11-17 18:43:26 -05:00
2026-11-09 01:22:35 -05:00
Let the database update get past 3.2.8 on installs whose tables have different collations, and on ones already stuck there: 3.2.8 matched license names against template names across software and software_templates, the second being one of the tables 2.1.6 to 2.4.1 created without a COLLATE, so where the server default is not utf8mb4_general_ci, MariaDB 11.5 and later, the comparison failed with Illegal mix of collations after the two ALTERs above it had gone in, and every run after that stopped at the first of them with Duplicate column name software_template_id, short of 3.6.5 which puts those tables right; admin/database_updates.php now runs databaseCollationRepair before each update it applies as well as after the last, so no update meets two collations whatever version it starts from, loads functions/database_collation.php itself when the process started on code from before it, and does not try a table again in the same run once it has failed, databaseCollationRepair taking a list of tables to skip; 3.2.8.php is changed in what it can get through and not in what it makes, each ALTER checked first so it can run again from wherever it stopped, the comparison naming its collation and the UPDATE leaving licenses that already have a template; every update from 2.0.7 to 3.6.5 was run on MariaDB with those 22 tables in utf8mb4_uca1400_ai_ci and 3.2.8 was the only one that failed, then the whole history run through the new runner with the tables put wrong before every update, on an install left as the forum report had it and from a process started on older code; CONTRIBUTING.md records the exception to never editing a shipped migration and the 26.11.7 changelog section has the fix
2026-11-11 21:13:02 -05:00
Add a collation check and repair to Admin > Debug: functions/database_collation.php reads from db.sql each table's default collation and each text column's, compares them with information_schema and can give every table that differs the collation db.sql has for it, one ALTER a table with a MODIFY a column built from its SHOW CREATE TABLE line with only the collation replaced, as database 3.6.5 does, so a binary column that was flattened goes back to utf8mb4_bin too and no column type changes; the ITFlow section gains a Database collation check that warns when any table differs, and the Database card lists them under Structure a row a table, in Copy for support as well, with a Repair collations button behind a confirm; the button posts to the new admin/post/debug.php, CSRF-checked and not tied to the request so a large table is not cut off with the browser, which writes an audit log entry naming the tables changed and a warning in App Logs for each one it had to leave, a table being changed whole or not at all; tables and columns db.sql does not have are not looked at; run through the page and against the whole schema on MySQL 8.0 and MariaDB 10.11; add both to the 26.11.7 changelog section
2026-11-11 20:33:19 -05:00
2026-11-09 01:22:35 -05:00
2026-11-18 01:52:00 -05:00
2026-11-19 00:37:39 -05:00
2026-10-20 11:30:27 -04:00
2026-11-17 19:24:04 -05:00
Emails stage 3: every email now goes through emailQueue and the shared layout - the client portal invite sends a link to set a password (or to sign in with Microsoft) instead of the password itself, offered on New Contact as well as Edit through portalMailInvite, with Forgot password, password changed and two-step sign-in emails through portalMailPasswordReset and portalMailAccountChange; shared link and code emails with the note quoted and the whole link printed under the button, replacing shareMailHtml and shareQueueMail; calendar invitations, updates and cancellations with when, repeats, where, the description and a join button; Email on the contacts and clients lists in the layout from one of the configured mailboxes with an optional greeting and send time, leaving out archived contacts and contacts without an address, each address once, nothing queued without mail set up, through emailBulkSend and emailBulkPost with a shared bulk_email_fields window; Admin > Mail > Previews shows all 52 emails built by their real senders on sample records inside a rolled-back transaction with emailQueue capturing and custom actions off, with computer and phone widths and Send me a copy; emailHtml gains content and button show_url, emailQueue gains queued_at and always so billing still queues as before, plus emailMailboxes and emailTestSend; ticketMailCreated, ticketMailReply, ticketMailWatchersAdded, ticketMailTaskApproval, ticketMailClosedReply, ticketSlaAlert and billingMailCardSaved moved into functions; fixes Email on the contacts list queuing mail to contacts with no address, the clients list including archived contacts, and both taking any From address posted; changelog updated
2026-10-17 23:26:25 -04:00
2026-11-16 19:36:00 -05:00
Make managed mode off by default and turned on per side in config.php - $config_enable_managed_instances = true; adds Admin > Managed Instances, the api/managed endpoints and the Managed Instances cron job, and $config_enable_managed_by = true; (or $config_manager_required = true;) adds Admin > Managed By, the Manager Check-in cron job and support sign-in; with a side off its menu entry, pages, modal, post handler and cron job are gone, the manager endpoints answer 503 so instances keep their connection and retry, a connected instance stops checking in and its locks, read-only and suspended lift while its connection is kept, any open support session is ended, and the support user still takes no seat; new managerEnabled(), managedEnabled() and managedConnected(), the cron registry and health check leave out the jobs of a side that is off, changelog updated
2026-11-05 20:17:42 -05:00
2026-11-09 01:22:35 -05:00
Set up a hosted instance and connect it in one command - Add Instance takes the address it will have, and the instance page gives a ready setup_cli command with the connection code and the client's company name, address, phone, website, tax ID, currency and primary contact as the first admin; setup_cli gains --manager-code and --manager-required (connects after setup, writes the managed line to config.php, exits 3 if it set up but could not connect), --ask-missing, --generate-password, --json and ITFLOW_SETUP_ environment variables for any option, and shows the cron job as a crontab line and for a hosting panel with the full PHP path; Managed Instances shows a connected instance whose cron has never run as Waiting for its cron job with the command to add, and the Managed Instances job says so in its notification; new managedSetupCommand(), the cron command in the instance report and the waiting state in managedInstanceHealth(), changelog updated
2026-11-06 14:29:27 -05:00
Robustness: lists take page 1 at least and an open end date, portal sessions go to the portal from the main address, custom page forms no longer load a missing post/ai.php, cron jobs that stop with an error code show as Failed with the parser saying what the mail server answered, the mail queue keeps a refreshed OAuth token for the rest of the run, the update check keeps the newest 100 commits and counts them all, restore_cli works on a database with no settings yet, the API reads a non-JSON body as no fields and clamps limit and offset, API client delete removes the client's uploads, contact anonymizing redacts stored values longest first, the asset transfer log names the asset, the client duplicate check escapes wildcards, and Access Modules drops its dead buttons and sorts only on its own columns; 26.11.9 changelog entries
2026-11-17 16:15:23 -05:00
2026-11-17 23:49:02 -05:00
Module switches: Dispatch, Bookkeeping, Purchasing, Trips and Calendar can be switched off in Admin > Settings > Modules, Dispatch coming with ticketing and the other three with invoicing, each hidden from menus, dashboard, search, reports and the API and refused on its pages, windows and handlers while off; Purchasing starts off unless already in use, Bookkeeping off posts the default accounts in place of account pickers, database 3.9.4, new moduleOn, moduleOffText and bookkeepingAccount helpers, purchase order settings tile summary, 26.11.9 changelog entries
2026-11-18 14:27:16 -05:00
Module switches: Dispatch, Bookkeeping, Purchasing, Trips and Calendar can be switched off in Admin > Settings > Modules, Dispatch coming with ticketing and the other three with invoicing, each hidden from menus, dashboard, search, reports and the API and refused on its pages, windows and handlers while off; Purchasing starts off unless already in use, Bookkeeping off posts the default accounts in place of account pickers, database 3.9.4, new moduleOn, moduleOffText and bookkeepingAccount helpers, purchase order settings tile summary, 26.11.9 changelog entries
2026-11-18 14:27:16 -05:00
2026-11-09 01:22:35 -05:00
2026-11-18 01:52:00 -05:00
Add RMM Providers under Admin > Integrations to bring devices in from an RMM as assets, with Tactical RMM as the first kind: a providers list (search, sort, add, edit, test, sync now, turn off and on, delete), a Clients page per provider to link its clients to ITFlow clients with same-name suggestions, devices matched to existing assets by serial or unique name or made as new ones, each asset field following the RMM until it is edited in ITFlow, removed devices marked and returned ones picked up, deleted assets left out until Bring back, a card per RMM device on the asset page with online state, last seen, signed-in user, reboot, patches and failing checks, Take Control and dashboard links, the state on the quick look, a status dot and RMM filter on the assets list, and the RMM Sync cron job every 15 minutes across every provider that is on; shared engine in functions/rmm.php and the Tactical adapter in functions/rmm_tactical.php so another RMM is one file and one registry line; database 3.6.7 adds rmm_providers, rmm_clients and rmm_devices; demo mode locks the new pages and handlers; 26.11.9 changelog entries
2026-11-13 18:13:58 -05:00
2026-11-13 18:44:58 -05:00
Admin lists on the standard list pattern: Ticket Templates, Roles, API Keys, Taxes, Categories and Tags now have the full-size search with the dark button, Active and Archived pills with counts, sortable table-light column headings, paging through filter_footer.php with records per page, and the btn-light row menu, with old archived=1 links still opening Archived; Ticket Templates sorts by name, tasks, use or last use, gains a Last used column and moves Import, Export, the report and Starter templates onto the New button's split menu; Roles sorts by name with admin roles first, agents or last change; API Keys sorts by name, end date, agent or last use, with Active and Expired pills so a revoked key moves to Expired to be deleted; Taxes sorts by name, rate or use; Categories and Tags keep their kinds in the left nav with the pills beside the list, sort by name or use (and in order for the ordered category kinds), and page in PHP; dragging categories into order and Move up and Move down work on every page (reorder_categories takes offset); bulk actions move to the right of the search row; descriptions wrap so rows and their menus fit on a phone; the help lines above the lists are dropped, with a category kind's purpose on its nav link; apiKeyRows() removed as unused; category and tag redirects use show=archived; changelog updated
2026-10-18 02:26:56 -04:00
Payment Providers stage 2: Saved Cards rebuilt in the standard list pattern showing whose card it is, the card brand and last four digits, expiry with expired and soon flags, and the recurring invoices that autopay with it and their next date, flagging an expired card on autopay as one that will be declined; adds All, On autopay and Expired tabs with counts, client and provider filters, search by customer and payment method ID, and sort by expiry; the Payment Providers list links to each provider's cards and autopay; removing a card names the autopay that stops, detaches it at Stripe, records the stopped autopay in each recurring invoice's history and states when Stripe could not be reached
2026-10-20 15:26:22 -04:00
Agent banners: a note along the top of agents' pages for one client or every client, shown as Notice, Heads up or Urgent between its start and end; a client's is added from New Banner in the client's menu, which lists its banners to change, and shows on its pages and on its tickets, invoices, quotes, recurring invoices and projects opened on their own; Admin > Agent Banners lists them all and adds them for every client; Notice and Heads up can be hidden per agent until the banner changes, Urgent is big and red and can't be hidden; kept in portal_announcements with a new announcement_audience column and an announcement_dismissals table (database 3.7.2), sharing the portal announcement form, now includes/announcement_form.php; 26.11.9 changelog entries
2026-11-17 13:44:49 -05:00
2026-11-17 21:28:45 -05:00
Module switches: Dispatch, Bookkeeping, Purchasing, Trips and Calendar can be switched off in Admin > Settings > Modules, Dispatch coming with ticketing and the other three with invoicing, each hidden from menus, dashboard, search, reports and the API and refused on its pages, windows and handlers while off; Purchasing starts off unless already in use, Bookkeeping off posts the default accounts in place of account pickers, database 3.9.4, new moduleOn, moduleOffText and bookkeepingAccount helpers, purchase order settings tile summary, 26.11.9 changelog entries
2026-11-18 14:27:16 -05:00
Bill sign-ups through the API and follow up when an invoice is paid - a lead that pays an invoice in full becomes a client however it is paid (online, autopay, a recorded payment or a batch), with the new A lead that pays an invoice becomes a client switch in Admin > Settings > Invoices and billing, on by default; a non-billable open ticket tied to an invoice (one raised through the API with ticket_invoice_id, or a quote's tickets once it becomes the invoice) gets an internal note when the invoice is paid in full, goes from On Hold back to Open, and its assigned agent is notified in the app and by email, while billable tickets whose time is on an invoice are left alone; new API endpoints recurring_invoices/create (lines from products or spelled out, the client's currency, frequency, start date, optional first invoice made at once and emailed to the primary and billing contacts, or marked Sent so its link can be paid, the answer including the invoice reference, amount, due date and pay link), recurring_invoices/read and portal_invites/create (sent from the company rather than the key's agent); tickets/create takes ticket_status (an active status other than Resolved and Closed), ticket_invoice_id (one of the client's own invoices) and ticket_notify agents to tell only the team; database 3.5.9 adds settings.config_invoice_paid_lead_to_client; invoicePaidFollowUp() runs from triggerCustomAction() on invoice_pay, with recurringInvoiceCreate(), billingInvoiceIssue() and the paid kind of ticketAgentEmailContent() in support; the Clients list reads each contract's term, so Renews soon shows again and its PHP warning is gone; changelog updated
2026-11-05 19:00:16 -05:00
Knowledge Base stage 2: who can read each article - agents only, clients (all, by client tag or by name) or anyone - database 3.9.6 with kb_article_visibility, kb_article_all_clients, kb_article_client_tags, kb_article_clients and config_kb_public_enable, Help in the client portal with search, categories, print and Ask us, the public help center at guest/kb.php with its switch in Admin > Settings > Knowledge Base and a link on the sign-in page, a Who can read it column, filter and article panel, tag merge moving article client tags, tagKinds only listing kb_article once its table exists, and changelog entries
2026-11-18 17:36:51 -05:00
Settings stage 1: add a Settings overview with a tile and current summary for every page, attention items for problems and a Find a setting search that opens the setting highlighted, add a shared settings frame with described sections, a save bar with unsaved state and Undo, a leave-page warning, server-side validation that keeps typed values and audit entries listing each change from old to new, and move Company details, Localization, Theme, Modules and Telemetry onto it with logo and favicon previews, the company phone following the country, a localization sample, a live theme preview, white-label key checks and Telemetry as a single switch
2026-10-20 11:29:24 -04:00
2026-10-20 12:56:01 -04:00
2026-11-17 23:49:02 -05:00
Knowledge Base stage 1: articles written once for every client in a new main-menu Knowledge Base, with title, summary, category, tags, editor content and pictures, drafts and publishing, a version kept on every edit and restorable, review cadence with Review due, the standard list with search, category and tag filters, views and bulk actions, copying an article or a client document into a draft, global search group and shortcut, Knowledge Base category kind, article tag kind without a client, audit log kind and Modules switch, database 3.9.5, 26.11.9 changelog entries
2026-11-18 16:53:57 -05:00
2026-11-17 22:40:30 -05:00
2026-11-17 21:26:50 -05:00
Purchasing: new To Order, Purchase Orders and Receiving pages under a Purchasing side menu section, with invoicing on and the new Purchasing role permission (module_procurement, Read, Modify, Full); items go on To Order by hand, from a product's Order button or from low-stock products, purchase orders are made from ticked items with their own prefix and next number, edited as drafts, downloaded as a PDF or emailed to the vendor and marked ordered, with optional approval over an amount that notifies the approvers by notice and email, carrier tracking links, receiving into stock or into client assets with serials, undoing a receipt, and recording the vendor bill as an expense linked to the received stock; agents only see purchase orders for clients they can reach, the Full access refusal says what Full allows for Purchasing, new functions/purchase_orders.php and a Purchase orders settings page, database 3.9.3 adds order_items, purchase_orders, po_items, po_receipts and po_tracking with four settings columns, 26.11.9 changelog entries
2026-11-18 00:45:43 -05:00
2026-11-17 21:25:57 -05:00
2026-11-16 18:17:49 -05:00
Settings stage 1: add a Settings overview with a tile and current summary for every page, attention items for problems and a Find a setting search that opens the setting highlighted, add a shared settings frame with described sections, a save bar with unsaved state and Undo, a leave-page warning, server-side validation that keeps typed values and audit entries listing each change from old to new, and move Company details, Localization, Theme, Modules and Telemetry onto it with logo and favicon previews, the company phone following the country, a localization sample, a live theme preview, white-label key checks and Telemetry as a single switch
2026-10-20 11:29:24 -04:00
Settings stage 1: add a Settings overview with a tile and current summary for every page, attention items for problems and a Find a setting search that opens the setting highlighted, add a shared settings frame with described sections, a save bar with unsaved state and Undo, a leave-page warning, server-side validation that keeps typed values and audit entries listing each change from old to new, and move Company details, Localization, Theme, Modules and Telemetry onto it with logo and favicon previews, the company phone following the country, a localization sample, a live theme preview, white-label key checks and Telemetry as a single switch
2026-10-20 11:29:24 -04:00
2026-11-17 17:55:25 -05:00
Knowledge Base stage 2: who can read each article - agents only, clients (all, by client tag or by name) or anyone - database 3.9.6 with kb_article_visibility, kb_article_all_clients, kb_article_client_tags, kb_article_clients and config_kb_public_enable, Help in the client portal with search, categories, print and Ask us, the public help center at guest/kb.php with its switch in Admin > Settings > Knowledge Base and a link on the sign-in page, a Who can read it column, filter and article panel, tag merge moving article client tags, tagKinds only listing kb_article once its table exists, and changelog entries
2026-11-18 17:36:51 -05:00
2026-11-18 01:52:00 -05:00
2026-11-13 03:04:21 -05:00
2026-11-09 01:22:35 -05:00
2026-11-18 01:52:00 -05:00
Show each starter content item as it will look under Pick which - a tag as its pill, a category as its chip, a product with its price and billing, with what each is for - and Preview the whole of a ticket, project, document, vendor or license template, canned response or product in a window, the words filled in as it is used marked; Maintenance > Starter Content gets Pick which too, its Add bringing only what is ticked and Will be added following the ticks, sharing admin/includes/starter_content_pick.php, admin/starter_content_preview.php and js/starter_content.js with Get started
2026-10-25 15:04:11 -04:00
2026-11-09 01:22:35 -05:00
2026-11-09 01:22:35 -05:00
Admin lists on the standard list pattern: Ticket Templates, Roles, API Keys, Taxes, Categories and Tags now have the full-size search with the dark button, Active and Archived pills with counts, sortable table-light column headings, paging through filter_footer.php with records per page, and the btn-light row menu, with old archived=1 links still opening Archived; Ticket Templates sorts by name, tasks, use or last use, gains a Last used column and moves Import, Export, the report and Starter templates onto the New button's split menu; Roles sorts by name with admin roles first, agents or last change; API Keys sorts by name, end date, agent or last use, with Active and Expired pills so a revoked key moves to Expired to be deleted; Taxes sorts by name, rate or use; Categories and Tags keep their kinds in the left nav with the pills beside the list, sort by name or use (and in order for the ordered category kinds), and page in PHP; dragging categories into order and Move up and Move down work on every page (reorder_categories takes offset); bulk actions move to the right of the search row; descriptions wrap so rows and their menus fit on a phone; the help lines above the lists are dropped, with a category kind's purpose on its nav link; apiKeyRows() removed as unused; category and tag redirects use show=archived; changelog updated
2026-10-18 02:26:56 -04:00
2026-11-18 01:52:00 -05:00
2026-11-18 01:52:00 -05:00
2026-11-17 17:52:35 -05:00
2026-11-09 01:22:35 -05:00
2026-11-18 01:52:00 -05:00
Robustness: lists take page 1 at least and an open end date, portal sessions go to the portal from the main address, custom page forms no longer load a missing post/ai.php, cron jobs that stop with an error code show as Failed with the parser saying what the mail server answered, the mail queue keeps a refreshed OAuth token for the rest of the run, the update check keeps the newest 100 commits and counts them all, restore_cli works on a database with no settings yet, the API reads a non-JSON body as no fields and clamps limit and offset, API client delete removes the client's uploads, contact anonymizing redacts stored values longest first, the asset transfer log names the asset, the client duplicate check escapes wildcards, and Access Modules drops its dead buttons and sorts only on its own columns; 26.11.9 changelog entries
2026-11-17 16:15:23 -05:00
2026-11-17 19:24:04 -05:00
2026-11-09 01:22:35 -05:00
2026-11-18 01:52:00 -05:00