Tickets: more than one agent can work a ticket - Additional agents under Assigned to adds helpers while the ticket stays with its lead, each booked with the lead, at a time of their own or not booked, finding it under Mine and on the dashboard, emailed the client's replies and sent their own booking with a calendar file; the tickets list and board show +1 or Helping, and helper bookings show on the calendar in the helper's color, can be dragged to a time of their own, appear in calendar links and count in double-booking warnings; database 3.8.5 adds ticket_helpers; 26.11.9 changelog entries

This commit is contained in:
johnnyq
2026-11-17 20:54:44 -05:00
parent bf1124570b
commit 9260da0cbc
17 changed files with 939 additions and 14 deletions

22
db.sql
View File

@@ -4059,6 +4059,28 @@ CREATE TABLE `ticket_fill_ins` (
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Table structure for table `ticket_helpers`
--
DROP TABLE IF EXISTS `ticket_helpers`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8mb4 */;
CREATE TABLE `ticket_helpers` (
`ticket_id` int(11) NOT NULL,
`user_id` int(11) NOT NULL,
`follows_lead` tinyint(1) NOT NULL DEFAULT 1,
`schedule_start` datetime DEFAULT NULL,
`schedule_end` datetime DEFAULT NULL,
`added_by` int(11) NOT NULL DEFAULT 0,
`added_at` datetime NOT NULL DEFAULT current_timestamp(),
PRIMARY KEY (`ticket_id`,`user_id`),
KEY `ticket_helpers_user` (`user_id`),
CONSTRAINT `ticket_helpers_ticket` FOREIGN KEY (`ticket_id`) REFERENCES `tickets` (`ticket_id`) ON DELETE CASCADE,
CONSTRAINT `ticket_helpers_user` FOREIGN KEY (`user_id`) REFERENCES `users` (`user_id`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Table structure for table `ticket_history`
--