From 4078fa5f251c690fab74f7f97ed9cbd0347294ad Mon Sep 17 00:00:00 2001 From: johnnyq Date: Tue, 17 Nov 2026 18:19:56 -0500 Subject: [PATCH] Tickets: a note with time worked keeps when it was worked, a date, start and end under Time worked filled from the timer until typed, with typed times setting the time worked, shown beside the time in the conversation and changed in Edit reply; database 3.7.8 adds ticket_replies.ticket_reply_work_start and ticket_reply_work_end; 26.11.9 changelog entries --- CHANGELOG.md | 4 +- admin/database_updates/3.7.8.php | 32 ++++ agent/js/ticket_work_times.js | 192 ++++++++++++++++++++++ agent/modals/ticket/ticket_reply_edit.php | 34 +++- agent/post/ticket.php | 40 ++++- agent/ticket.php | 54 ++++-- db.sql | 2 + functions/ticket.php | 87 ++++++++++ 8 files changed, 421 insertions(+), 24 deletions(-) create mode 100644 admin/database_updates/3.7.8.php create mode 100644 agent/js/ticket_work_times.js diff --git a/CHANGELOG.md b/CHANGELOG.md index ed7a71f51..f72431532 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,7 +6,7 @@ This file documents all notable changes made to ITFlow. ### Upgrading -Update from Maintenance > Update — Queue Update hands the job to cron, which updates the files and applies this release's eleven database changes (3.6.6 to 3.7.7) in the same pass. They add four tables for RMM providers and their alerts, a setting for device actions and one for API keys in the address, a column marking the emails the mail queue clears once sent, a column and a table for agent banners, two columns for ticket statuses with a setting for the "ticket assigned" message, a column on tickets with a setting for the "no response" message, a table for who a ticket's email replies go to, the settings for Quick tickets, and columns on recurring tickets and recurring invoices for booking and making them ahead, and change nothing that is there. Nothing else is required. This release has eleven security fixes - see Security. On Apache, ITFlow's own .htaccess now sends security headers: if you show ITFlow inside a frame on another website, it will now refuse to load there. On nginx, add the same headers to your server block if you want them - see Developer Updates. +Update from Maintenance > Update — Queue Update hands the job to cron, which updates the files and applies this release's twelve database changes (3.6.6 to 3.7.8) in the same pass. They add four tables for RMM providers and their alerts, a setting for device actions and one for API keys in the address, a column marking the emails the mail queue clears once sent, a column and a table for agent banners, two columns for ticket statuses with a setting for the "ticket assigned" message, a column on tickets with a setting for the "no response" message, a table for who a ticket's email replies go to, the settings for Quick tickets, columns on recurring tickets and recurring invoices for booking and making them ahead, and two columns on ticket replies for when their time was worked, and change nothing that is there. Nothing else is required. This release has eleven security fixes - see Security. On Apache, ITFlow's own .htaccess now sends security headers: if you show ITFlow inside a frame on another website, it will now refuse to load there. On nginx, add the same headers to your server block if you want them - see Developer Updates. ### Security @@ -85,6 +85,7 @@ Update from Maintenance > Update — Queue Update hands the job to cron, which u - Tickets: Email reply has a To line. It starts with the contact, the watchers and anyone at the client who asked for every update on their company's tickets; the technician it's assigned to, the client's other contacts or any email address typed in can be added, and anyone taken out. Everyone in To gets the email, each told why. What was changed is kept for the ticket, so its next email reply starts with the same people - taking a watcher out of To doesn't stop them watching. A reply sent to several tickets at once still goes to each one's contact and watchers. From Mountaineer IT's build of ITFlow. - Tickets: Quick ticket - the + in the top bar, on every page - is for a call or someone at your desk: the client (on a client's page, that one), the contact, found by name, email address or phone number, and what the issue is. The contact's tickets still open are listed first, with who has each, so the same problem isn't raised twice - Work on this one goes to one of them instead, with its timer running. Make ticket raises it as New Ticket would and opens it with its timer already running. Admin > Settings > Tickets, Quick tickets, sets what these tickets start with: who they go to, the status, priority, category and billing, when the timer starts, whether the contact starts on the client's primary and whether they're emailed. From Mountaineer IT's build of ITFlow. - Tickets: a stopwatch in the top bar shows the ticket timers running or paused in your browser, pulsing while one runs, so time isn't lost on a ticket you moved away from. It lists each ticket and its time, to go back to it, pause or resume the timer, or throw its time away. From Mountaineer IT's build of ITFlow. +- Tickets: a note with time worked keeps when the work was done. Under Time worked, When it was worked has the date, start and end - filled in from the timer, ending now, until you type them, and typed times set the time worked, for a visit or a call written up later. The conversation shows it beside the time ("25m (Tue Nov 17, 2:05 - 2:30 PM)"), and Edit changes it: new times set the time worked, and a new time worked alone moves the start. An end before the start runs past midnight. A note with time worked needs a date, start and end to send. From Mountaineer IT's build of ITFlow. - Recurring tickets: on Schedule, Book the work for takes a time and Remote or Onsite - each ticket raised is booked for its run day at that time, with the emails, calendar invite and note booking it on the ticket gives. Make it ahead raises each ticket so many days before its run day, which stays the day the work is for - or so many days before the 1st of its month, so every run in a month is raised on one day (monthly and longer repeats). The window says when the next one will be made, and the list shows the time and days ahead. Raise now books the ticket for its run too. From Mountaineer IT's build of ITFlow. - Recurring invoices: Make it ahead makes each invoice so many days before its date, dated the day it's made, and Due, when made ahead sets it due on its date plus the client's terms, or on its date. With 0 days nothing changes. From Mountaineer IT's build of ITFlow. @@ -203,6 +204,7 @@ Update from Maintenance > Update — Queue Update hands the job to cron, which u - Database 3.7.5: `ticket_mail_choices` - per ticket, the addresses put in or taken out of the To line where that differs from the default (the contact, watchers and `ticketColleagueRecipients()` in; the assigned agent, the client's other contacts and typed addresses out), going with the ticket. `functions/ticket_reply_recipients.php`: `ticketReplyRecipients()` lists who the To line offers, `ticketReplyRecipientsPick()` keeps the posted choice and returns `emailQueue()` recipients with why each gets it, `ticketReplyRecipientsForget()` clears it. `add_ticket_reply` sends to them when `email_to_shown` is posted with `email_to[]`, through `ticketMailReply()`'s new `$to` and `ticketMailSend()`'s `recipients` option; without it - the bulk reply, the API, an older form - to the contact and watchers as before. `change_client_ticket` takes off watchers who are neither agents nor the new client's contacts, and forgets the ticket's choices. From Mountaineer IT's build of ITFlow. - Database 3.7.6: `config_quick_ticket_on`, `_assign` ('me', 'nobody' or a user id), `_status`, `_priority`, `_category`, `_billable` (-1 is `config_ticket_default_billable`), `_timer` (make, open or off), `_primary`, `_open_tickets` and `_email_client` in `settings`, read by `quickTicketSettings()` (`functions/quick_ticket.php`). `includes/top_nav.php` has the + (an `ajax-modal` of `agent/modals/ticket/ticket_quick.php`, with `agent/js/ticket_quick.js`) and the timers menu (`js/ticket_timers.js`, loaded from `includes/footer.php`). The window posts `add_ticket` with `quick_ticket`, plain-text `details` (made HTML by `quickTicketDetailsHtml()`), `status`, `category_id`, `billable` and `quick_ticket_timer`, the browser's clock in ms; `add_ticket` skips `ticketMailCreated()` when `_email_client` is off and calls `quickTicketAfterCreate()`, which logs the history line and keeps the start in the session for `quickTicketTimerScript()`, printed on the ticket page before `agent/js/ticket_time_tracking.js`. `agent/ajax.php`: `ticket_also_open` takes `work` (who has each, when it last moved, a Work on this one button with `data-ticket-work`, up to 10, and a line when there are none), `get_client_contacts` also returns `contact_phone` and `contact_mobile`, and `ticket_timer_tickets` returns the reference, subject, client and state of the tickets behind the timers the agent can open. The timers read and write the same `-startTime`, `-pausedTime` and `ticket-timer-running-` keys, and on the ticket's own page press its `#startStopTimer`. From Mountaineer IT's build of ITFlow. - Database 3.7.7: `recurring_tickets.recurring_ticket_schedule_time` (NULL books nothing), `_schedule_onsite`, `_lead_days` and `_lead_mode` (days or month), and `recurring_invoices.recurring_invoice_lead_days` and `_due_mode` (terms or next) - `recurringAheadReady()`. The nightly job takes recurring tickets by `recurringTicketDueSql()` and recurring invoices up to `recurring_invoice_lead_days` ahead, made with `recurringInvoiceGenerate()`'s `$early` when the date is still to come. `recurringTicketRunNow()` calls `recurringTicketBook()`, which books through `ticketSetSchedule()` for the run day at the time (today for a missed run), as "Recurring ticket" from the cron; `recurringInvoiceGenerate()` dates an invoice made ahead with lead days due by `recurringInvoiceAheadDue()`. Days ahead are kept short of one step by `recurringTicketLeadDays()` and `recurringInvoiceLeadDays()` (a month is 28 days, 90 at most; 27 before the 1st of the month, month-based repeats only). The fields are `schedule_time`, `schedule_onsite`, `lead_days` and `lead_mode` on the recurring ticket windows (`agent/includes/inc_recurring_ticket_ahead.php`), and `lead_days` and `due_mode` on the recurring invoice form; a post without `lead_days` keeps what is saved. From Mountaineer IT's build of ITFlow. +- Database 3.7.8: `ticket_replies.ticket_reply_work_start` and `ticket_reply_work_end`, in company time - `ticketWorkTimesReady()`. `add_ticket_reply` takes `work_date`, `work_start` and `work_end` (`ticketWorkRange()`; an end before the start is the next day, under 24 hours) for a note with time worked, and `ticketWorkTimeWorked()` makes the time worked their length unless it agrees to the minute; without them, or from the bulk reply, the API or email, they stay NULL - it ended when it was posted. `edit_ticket_reply` takes the same fields: changed times set the time worked, the same times with a new time worked move the start, times left as `ticketWorkTimesShown()` filled them on a note without any keep it without, and no time worked clears them. The reply box's time row is Time worked and When it was worked, above Status and Send; `agent/js/ticket_work_times.js` follows `#hours` / `#minutes` / `#seconds` from `ticket_time_tracking.js` (at least a minute), in company time from `#workTimes` `data-now`, and refuses the form in the capture phase, before the timer resets, when a note with time worked has no valid times. From Mountaineer IT's build of ITFlow. ## [26.11.8] diff --git a/admin/database_updates/3.7.8.php b/admin/database_updates/3.7.8.php new file mode 100644 index 000000000..005a800e3 --- /dev/null +++ b/admin/database_updates/3.7.8.php @@ -0,0 +1,32 @@ + 0; + }; + + if (!$itflow_column('ticket_replies', 'ticket_reply_work_start')) { + mysqli_query($mysqli, "ALTER TABLE `ticket_replies` ADD `ticket_reply_work_start` datetime DEFAULT NULL AFTER `ticket_reply_time_worked`"); + } + + if (!$itflow_column('ticket_replies', 'ticket_reply_work_end')) { + mysqli_query($mysqli, "ALTER TABLE `ticket_replies` ADD `ticket_reply_work_end` datetime DEFAULT NULL AFTER `ticket_reply_work_start`"); + } diff --git a/agent/js/ticket_work_times.js b/agent/js/ticket_work_times.js new file mode 100644 index 000000000..83e3bf324 --- /dev/null +++ b/agent/js/ticket_work_times.js @@ -0,0 +1,192 @@ +/* + * When a note's time was worked - the date, start and end under Time worked + * in the reply box (agent/ticket.php; functions/ticket.php keeps them). + * + * Until they are typed they follow the timer (agent/js/ticket_time_tracking.js, + * which writes #hours / #minutes / #seconds): the work ends now and started the + * time worked ago. Typing a time pauses the timer and sets the time worked from + * the start and end; changing the time worked after that moves the start, and + * the end stays. "Use the timer" goes back to following it. + * + * The times are company time: "now" is the server's clock as the page was + * drawn (#workTimes data-now), moved on by this browser's, so an agent whose + * computer is in another time zone still gets the company's. + * + * A note with time worked needs a date, start and end that make sense to go - + * checked as the form is sent, before the timer resets. + */ +document.addEventListener('DOMContentLoaded', function () { + 'use strict'; + + const box = document.getElementById('workTimes'); + const h = document.getElementById('hours'); + const m = document.getElementById('minutes'); + const s = document.getElementById('seconds'); + const date = document.getElementById('work_date'); + const start = document.getElementById('work_start'); + const end = document.getElementById('work_end'); + const form = box ? box.closest('form') : null; + if (!box || !h || !m || !date || !start || !end || !form) { + return; + } + const mode = form.querySelector('[data-work-times-mode]'); + const problemLine = form.querySelector('[data-work-times-problem]'); + + // Company time: the page's clock, moved on by this browser's + const drawn = Date.parse(box.dataset.now || ''); + const shift = isNaN(drawn) ? 0 : drawn - Date.now(); + const now = () => new Date(Date.now() + shift); + + let typed = false; // the agent set the times themselves + + const pad = (n) => String(n).padStart(2, '0'); + const ymd = (d) => d.getFullYear() + '-' + pad(d.getMonth() + 1) + '-' + pad(d.getDate()); + const hm = (d) => pad(d.getHours()) + ':' + pad(d.getMinutes()); + + function worked() { + return (parseInt(h.value, 10) || 0) * 3600 + (parseInt(m.value, 10) || 0) * 60 + (s ? parseInt(s.value, 10) || 0 : 0); + } + + // The typed start to end in seconds - an end before the start runs past midnight - or null + function typedLength() { + if (!date.value || !start.value || !end.value) { + return null; + } + const from = new Date(date.value + 'T' + start.value); + const to = new Date(date.value + 'T' + end.value); + if (to <= from) { + // The next day by the calendar - adding a day's seconds is an hour out on the nights the clocks change + to.setDate(to.getDate() + 1); + } + const secs = (to - from) / 1000; + return secs > 0 && secs < 86400 ? secs : null; + } + + function setWorked(secs) { + h.value = pad(Math.floor(secs / 3600)); + m.value = pad(Math.floor((secs % 3600) / 60)); + if (s) { + s.value = '00'; + } + // The timer takes the new length from its fields + [h, m, s].forEach((el) => el && el.dispatchEvent(new Event('change', { bubbles: true }))); + } + + function pauseTimer() { + const button = document.getElementById('startStopTimer'); + if (button && button.querySelector('.fa-pause')) { + button.click(); + } + } + + // Following the timer: ends now, started the time worked ago + function follow() { + if (typed) { + return; + } + const secs = worked(); + const to = now(); + if (!secs) { + date.value = ymd(to); + start.value = ''; + end.value = ''; + return; + } + // At least a minute, so a few seconds on the timer still has a start before its end + const from = new Date(to.getTime() - Math.max(1, Math.round(secs / 60)) * 60000); + date.value = ymd(from); + start.value = hm(from); + end.value = hm(to); + } + + function showMode() { + mode.textContent = ''; + if (typed) { + mode.append('Typed by you · '); + const back = document.createElement('a'); + back.href = '#'; + back.textContent = 'use the timer'; + back.addEventListener('click', function (e) { + e.preventDefault(); + typed = false; + showMode(); + follow(); + showProblem(''); + }); + mode.append(back); + } else { + const icon = document.createElement('i'); + icon.className = 'fas fa-fw fa-link me-1'; + mode.append(icon, 'From the timer - type a time to set it yourself'); + } + } + + function problem() { + if (!worked()) { + return ''; + } + if (!date.value || !start.value || !end.value) { + return 'Add the date and the start and end of this work.'; + } + if (typedLength() === null) { + return 'The end has to be after the start, within a day.'; + } + return ''; + } + + function showProblem(text) { + problemLine.textContent = text; + problemLine.hidden = !text; + [date, start, end].forEach((el) => el.classList.toggle('is-invalid', !!text && !el.value)); + } + + [date, start, end].forEach(function (el) { + el.addEventListener('input', function () { + if (!typed) { + typed = true; + pauseTimer(); + showMode(); + } + const secs = typedLength(); + if (secs !== null) { + setWorked(secs); + } + showProblem(''); + }); + }); + + // A new time worked once the times are typed: the end stays, the start moves + [h, m, s].forEach(function (el) { + if (!el) { + return; + } + el.addEventListener('input', function () { + if (typed && date.value && end.value) { + const to = new Date(date.value + 'T' + end.value); + const from = new Date(to.getTime() - Math.round(worked() / 60) * 60000); + date.value = ymd(from); + start.value = hm(from); + } else { + follow(); + } + showProblem(''); + }); + }); + + // First, as the form goes - before the timer resets, which it does only for a reply that went + form.addEventListener('submit', function (e) { + follow(); + const why = problem(); + if (why) { + e.preventDefault(); + e.stopImmediatePropagation(); + showProblem(why); + (date.value ? start : date).focus(); + } + }, true); + + showMode(); + follow(); + // The timer writes its fields without events - follow it while it runs, and the clock + setInterval(follow, 5000); +}); diff --git a/agent/modals/ticket/ticket_reply_edit.php b/agent/modals/ticket/ticket_reply_edit.php index ff8a62d3f..aa2de574c 100644 --- a/agent/modals/ticket/ticket_reply_edit.php +++ b/agent/modals/ticket/ticket_reply_edit.php @@ -6,7 +6,8 @@ enforceUserPermission('module_support', 2); $ticket_reply_id = intval($_GET['id']); -$sql = mysqli_query($mysqli, "SELECT ticket_client_id, ticket_reply, ticket_reply_time_worked, ticket_reply_type, +$sql = mysqli_query($mysqli, "SELECT ticket_client_id, ticket_reply, ticket_reply_time_worked, ticket_reply_type, ticket_reply_created_at, + " . (ticketWorkTimesReady() ? 'ticket_reply_work_start, ticket_reply_work_end,' : 'NULL AS ticket_reply_work_start, NULL AS ticket_reply_work_end,') . " " . (ticketReplyEmailReady() ? 'ticket_reply_emailed, ticket_reply_emailed_to' : 'NULL AS ticket_reply_emailed, NULL AS ticket_reply_emailed_to') . " FROM ticket_replies LEFT JOIN tickets ON ticket_id = ticket_reply_ticket_id WHERE ticket_reply_id = $ticket_reply_id @@ -82,14 +83,33 @@ ob_start(); -
-
- -
- - +
+
+
+ +
+ + +
+ +
+
+ +
+ + + + - + +
+
Change the times and the time worked follows them. Change only the time worked and the start moves.
+
+
+
diff --git a/agent/post/ticket.php b/agent/post/ticket.php index 38caac42d..8432175bc 100644 --- a/agent/post/ticket.php +++ b/agent/post/ticket.php @@ -1137,6 +1137,13 @@ if (isset($_POST['add_ticket_reply'])) { // Time tracking, inputs & combine into string $ticket_reply_time_worked = escapeSql(sprintf("%02d:%02d:%02d", max(0, intval($_POST['hours'] ?? 0)), max(0, min(59, intval($_POST['minutes'] ?? 0))), max(0, min(59, intval($_POST['seconds'] ?? 0))))); + // When it was worked - typed times set the time worked; without them it ended as it was posted (functions/ticket.php) + $work_sql = ''; + if (ticketWorkTimesReady() && ticketTimeSeconds($ticket_reply_time_worked) > 0 + && ($work = ticketWorkRange($_POST['work_date'] ?? '', $_POST['work_start'] ?? '', $_POST['work_end'] ?? ''))) { + $ticket_reply_time_worked = ticketWorkTimeWorked($work, $ticket_reply_time_worked); + $work_sql = ", ticket_reply_work_start = '{$work[0]}', ticket_reply_work_end = '{$work[1]}'"; + } // Who sees it: internal note, public note, or public and emailed - or texted (functions/sms.php) $send_email = 0; @@ -1182,7 +1189,7 @@ if (isset($_POST['add_ticket_reply'])) { // Process reply actions, if we have a reply to work with (e.g. we're not just editing the status) if ($ticket_reply !== '') { - mysqli_query($mysqli, "INSERT INTO ticket_replies SET ticket_reply = '$ticket_reply', ticket_reply_time_worked = '$ticket_reply_time_worked', ticket_reply_type = '$ticket_reply_type', ticket_reply_by = $session_user_id, ticket_reply_ticket_id = $ticket_id"); + mysqli_query($mysqli, "INSERT INTO ticket_replies SET ticket_reply = '$ticket_reply', ticket_reply_time_worked = '$ticket_reply_time_worked' $work_sql, ticket_reply_type = '$ticket_reply_type', ticket_reply_by = $session_user_id, ticket_reply_ticket_id = $ticket_id"); $ticket_reply_id = mysqli_insert_id($mysqli); // Store any attached files against this reply before the email is built, so @@ -1361,7 +1368,36 @@ if (isset($_POST['edit_ticket_reply'])) { $ticket_reply = mysqli_real_escape_string($mysqli, $ticket_reply_html); $ticket_reply_time_worked = escapeSql(ticketTimeWorked($_POST['time'] ?? '')); - mysqli_query($mysqli, "UPDATE ticket_replies SET ticket_reply = '$ticket_reply', ticket_reply_type = '$ticket_reply_type', ticket_reply_time_worked = '$ticket_reply_time_worked' WHERE ticket_reply_id = $ticket_reply_id"); + /* + * When it was worked (functions/ticket.php). Changed times set the time worked; the + * same times with a new time worked move the start, and the end stays. A note without + * times keeps having none unless they are changed from what the window showed (ending + * when it was posted). No time worked, no times. + */ + $work_sql = ''; + if (ticketWorkTimesReady() && isset($_POST['work_date'])) { + $was = mysqli_fetch_assoc(mysqli_query($mysqli, "SELECT ticket_reply_created_at, ticket_reply_time_worked, ticket_reply_work_start, ticket_reply_work_end FROM ticket_replies WHERE ticket_reply_id = $ticket_reply_id")); + $seconds = ticketTimeSeconds($ticket_reply_time_worked); + $work = $seconds > 0 ? ticketWorkRange($_POST['work_date'], $_POST['work_start'] ?? '', $_POST['work_end'] ?? '') : null; + $minute = function (array $range) { + return substr($range[0], 0, 16) . substr($range[1], 0, 16); + }; + if ($work && empty($was['ticket_reply_work_start']) && $minute($work) === $minute(ticketWorkTimesShown($was))) { + $work = null; + } elseif ($work && !empty($was['ticket_reply_work_start']) && $minute($work) === $minute([$was['ticket_reply_work_start'], $was['ticket_reply_work_end']]) + && $seconds !== ticketTimeSeconds($was['ticket_reply_time_worked'])) { + $work[0] = date('Y-m-d H:i:s', strtotime($work[1]) - $seconds); + } elseif ($work) { + $ticket_reply_time_worked = ticketWorkTimeWorked($work, $ticket_reply_time_worked); + } + if ($work) { + $work_sql = ", ticket_reply_work_start = '{$work[0]}', ticket_reply_work_end = '{$work[1]}'"; + } elseif ($seconds <= 0) { + $work_sql = ", ticket_reply_work_start = NULL, ticket_reply_work_end = NULL"; + } + } + + mysqli_query($mysqli, "UPDATE ticket_replies SET ticket_reply = '$ticket_reply', ticket_reply_type = '$ticket_reply_type', ticket_reply_time_worked = '$ticket_reply_time_worked' $work_sql WHERE ticket_reply_id = $ticket_reply_id"); // Only the agents it mentions now that it didn't before are told $told = ticketMentionsTell($row, $ticket_reply_id, $ticket_reply_html, ticketMentionsSync($ticket_reply_id, $mentioned)); diff --git a/agent/ticket.php b/agent/ticket.php index 8c1a72049..95ddbf0ca 100644 --- a/agent/ticket.php +++ b/agent/ticket.php @@ -258,6 +258,7 @@ if (isset($_GET['ticket_id'])) { // Get ticket replies - with whether each of yours was emailed, and who to $sql_ticket_replies = mysqli_query($mysqli, "SELECT contact_name, contact_photo, ticket_reply, ticket_reply_by, ticket_reply_created_at, ticket_reply_id, ticket_reply_time_worked, ticket_reply_type, ticket_reply_updated_at, user_avatar, user_id, user_name, + " . (ticketWorkTimesReady() ? 'ticket_reply_work_start, ticket_reply_work_end,' : 'NULL AS ticket_reply_work_start, NULL AS ticket_reply_work_end,') . " " . (ticketReplyEmailReady() ? 'ticket_reply_emailed, ticket_reply_emailed_to' : 'NULL AS ticket_reply_emailed, NULL AS ticket_reply_emailed_to') . " FROM ticket_replies LEFT JOIN users ON ticket_reply_by = user_id @@ -914,8 +915,38 @@ if (isset($_GET['ticket_id'])) {
+ +
+
+ +
+ + + + + +
+
+ +
+ +
+ + + + - + +
+
+
+ + +
+ +
+
-
+
- -
- -
- - - - - -
-
- -
+