Ticket Merge Helper

WHAT IT DOES

Ticket Merge Helper is a browser extension that automatically scans the current webpage for ticket records, ticket IDs, subjects, statuses, and duplicate indicators. It detects ticket elements by examining class names, IDs, data attributes, and text patterns for ticket IDs (alphanumeric strings of 4-15 characters), subjects, and status indicators. The extension adds a floating "merge helper" button (🔀) next to each detected ticket element, allowing you to select individual tickets for bulk merging, capture ticket ID, subject, and status. Clicking the button toggles the selection state, and selected tickets are added to a bulk collection. The main panel allows you to select a primary ticket from the selected tickets, add notes about the merge reason, and merge all selected tickets into the primary ticket in configurable batches. The extension updates UI elements on the page to show merge status and logs each merge to the local database with primary ID, secondary IDs, notes, and tags. The main panel displays all saved merges with primary tickets, merged ticket IDs, notes, and tags. All data is stored locally in your browser using GM_setValue, ensuring your merge history persists across page reloads and browser sessions. This helps support agents, help desk managers, and customer service professionals to perform bulk ticket merges directly from ticket lists without manually opening each ticket, saving time on duplicate resolution and ticket consolidation.

WHERE IT RUNS

This extension runs on any support system or help desk page that displays ticket records, ticket IDs, subjects, statuses, or duplicate indicators – including Zendesk, Freshdesk, Jira Service Management, Salesforce Service Cloud, and any page containing ticket data. The extension intelligently adapts to different page structures and supports a wide range of common ticket display patterns. No manual configuration is required per site; the extension automatically detects ticket elements using a flexible pattern matching system. This makes it ideal for support agents, help desk managers, and customer service professionals who need to perform bulk merges directly from the ticket list.

HOW TO USE

Simply install the extension and navigate to any support system page displaying tickets. The extension automatically detects ticket elements and places a small "merge helper" button (🔀) next to each one. Click any of these buttons to select that ticket for merging – the button highlights to show it's selected. Click it again to deselect. As you select tickets, a counter at the bottom-right shows how many you've collected. When ready, click the floating button (🔗) to open the main panel. From the dropdown, select which ticket should be the primary ticket (the one that will remain after the merge). Add a note about the merge reason and optional tags. Click "Merge Selected Tickets" to start the bulk merge process – the extension processes secondary tickets in batches (configurable size, default 5) to avoid performance issues, marking merged tickets on the page and logging each merge. The panel also displays your merge history for reference. Use the settings section to enable or disable auto-detection and set the batch size. The "Clear All History" button removes all tracking data when needed.

ONE TECHNICAL SECTION – WHY IT WORKS

The extension employs a multi-layered detection system that identifies ticket information with high accuracy. First, it scans the DOM using a comprehensive set of CSS selectors targeting common ticket-related class patterns, IDs, and data attributes. The ticket ID extraction uses regex pattern matching to identify alphanumeric ticket identifiers (4-15 characters) from text, data attributes, and URL links. The subject extraction identifies ticket subjects from text patterns and data attributes. The status extraction identifies ticket statuses from text patterns, status badges, and data attributes. Each tracked ticket is assigned a unique ID based on the ticket ID, ensuring that history stays correctly associated. The bulk merge process uses a batched approach with configurable batch size (default 5), processing secondary tickets in sequential batches with 300ms delays between batches to avoid performance issues. The primary ticket selection ensures clear merge targets, and each merge is logged with full details. A MutationObserver detects dynamic content updates and re-scans only when new ticket elements appear, balancing real-time accuracy with system performance.

THE PANEL – DRAG / PER-SITE POSITION / SNAP / COLLAPSE / RESIZE / ESCAPE

The ticket merge panel includes a draggable title bar, allowing you to position it anywhere on screen for convenient access during ticket management. The extension remembers your preferred position per website, so the panel opens in the same location each time you return to that domain. The panel supports snap-to-edge behavior – when dragged near screen edges, it gently snaps into place for a tidy workspace layout. You can collapse the panel down to just its title bar by clicking the collapse button, keeping it accessible without taking up screen space. The merge history and settings are contained within a scrollable body, ensuring all content remains accessible even on smaller screens. Pressing the Escape key closes the panel instantly, returning you to your support workflow.

PLEASE NOTE

This extension requires the free BotGentz extension to be installed and enabled, as it relies on BotGentz's userscript injection and GM_* API shims for cross-browser compatibility. Websites frequently update their HTML structures and class names, which may cause ticket detection to break temporarily – we actively maintain the matching patterns and release updates regularly. The extension stores all merge data, merge history, and notes exclusively in your local browser storage (GM_setValue); no data is ever transmitted to any external server or third party. You are responsible for backing up your merge history data if you switch browsers or clear your storage. The extension does not read, modify, or interfere with any support system data, tickets, or functionality beyond the page content – it operates on the static page content and stores only metadata (ticket IDs, subjects, merge relationships, and notes) that you explicitly create. Use this tool responsibly and in accordance with your organization's data handling and ticket management policies.