Support Shift Handover Notes

WHAT IT DOES

Provides a structured tool for creating comprehensive support shift handover notes. The script displays a form with dedicated sections for Shift Date, Handover From/To, Open Tickets Summary, Escalations/Pending Issues, Critical Issues, Resolved Tickets, Customer Communications, Actions for Next Shift, Known Workarounds, and Notes. Each section can be filled with detailed handover information, and timestamps are auto-recorded. A summary view shows section completion status and automatically counts tickets within each section (detecting bullet points, numbered items, and ticket patterns like #TICKET-123). You can add custom sections, apply tags for categorization, and export notes as plain text, JSON, or email-ready HTML. Per-shift handover notes are saved by shift identifier and date.

WHERE IT RUNS

Works on all websites (match pattern *://*/*), making it perfect for support teams, NOC operators, help desk staff, and anyone who needs to hand over work between shifts. Each shift and date combination gets its own independent note set, allowing multiple teams to use the tool without mixing notes. Notes are saved per shift identifier and date, ensuring continuity across sessions and page reloads.

HOW TO USE

Install the script and the handover notes tool appears in the panel. Enter a shift identifier and team name to load or create notes for that shift. Fill in each section with your handover details. Add tags to categorize your notes (e.g., "urgent", "follow-up", "escalation"). The summary shows which sections are filled and automatically counts tickets from the text content. Use the export buttons to copy your notes as plain text, JSON, or formatted HTML suitable for email clients. The script saves your progress automatically as you work.

REAL MECHANISM: SHIFT-KEYED PERSISTENCE WITH TICKET COUNT HEURISTICS AND MULTI-FORMAT EXPORT

This script uses a shift-based storage architecture where each shift and date gets its own isolated handover note set. The getShiftId() retrieves the current shift identifier from GM_setValue or generates a new one, while getTodayString() returns the current date in YYYY-MM-DD format. Data is stored using GM_setValue with a key format of "handover_notes_" plus the shift ID and date, ensuring data isolation between shifts. The data structure includes an entries object where keys are section IDs and values are note text, plus tags array, createdAt timestamp, shiftId, date, and team. The ticket count heuristic uses a multi-pattern detection approach: it counts bullet points (•, -, *), numbered items (1., 2., etc.), and ticket pattern matches (#TICKET-, INC-, SR-, REQ- followed by digits). The function returns the sum of these counts or 1 if the section has content but no countable items. This provides a useful metric for shift handover summaries. The render function displays a count badge next to each section label showing the ticket count. The export functions generate three formats: plain text with section headers and item counts, JSON with the full data structure, and HTML with h2/h3 tags and paragraph elements for email compatibility. All operations are reactive, with automatic persistence through saveHandoverNotes() and re-render.

THE PANEL

Drag the panel anywhere on screen by clicking and holding the header. It snaps to screen edges when released. Collapse it to a small bubble by clicking the minimize button, and expand it back by clicking the bubble. Resize the panel from any corner. Press Escape to close the configuration panel. Your position and size preferences are saved automatically per site.

PLEASE NOTE

This script requires the free BotGentz browser extension which provides the BGPanel framework and storage APIs. All data (notes, tags, sections, shift identifiers, and team names) is stored locally in your browser using GM_setValue and never sent anywhere. No analytics, no tracking, no external calls. The script only reads the current shift identifier and date to isolate notes and never accesses user data, passwords, or sensitive information. Notes are saved per shift identifier and date, so ensure each shift uses a consistent identifier.