Incident Timeline Recorder

WHAT IT DOES

Provides a structured incident timeline recorder for tracking events during incident response and troubleshooting. The script displays a chronological timeline where you can record events as they happen, with configurable event types including Incident Detected, Alert Acknowledged, Investigation Started, Root Cause Identified, Mitigation Applied, Service Restored, Customer Communication, Post-Incident Review, and Incident Closed. Each event is automatically timestamped, and you can add descriptions and notes to capture important details. Events are color-coded by category for quick visual scanning. The timeline can be exported as formatted text or JSON for post-incident reviews, compliance reporting, and documentation.

WHERE IT RUNS

Works on all websites (match pattern *://*/*), making it perfect for incident management platforms, monitoring dashboards, SRE consoles, operations portals, or any web-based incident response workflow. Each incident gets its own independent timeline, allowing you to manage multiple incidents simultaneously. The timeline state is saved per incident identifier, ensuring continuity across sessions and page reloads.

HOW TO USE

Install the script and the incident timeline recorder appears in the panel. Enter an incident identifier to associate the timeline with a specific incident. Select an event type from the dropdown (or add custom types), optionally add a description and notes, then click "Add Event" to record it. The event appears in the timeline with its timestamp and color-coded category. Add custom event types for your specific incident response process. Use the export buttons to copy the timeline as text or JSON to your clipboard for use in post-incident reviews, reports, or documentation. The script saves your progress automatically as you work.

REAL MECHANISM: INCIDENT-KEYED TIMELINE PERSISTENCE WITH COLOR-CODED CATEGORIZATION AND MULTI-FORMAT EXPORT

This script uses an incident-based storage architecture where each incident gets its own isolated timeline state. The getIncidentId() function retrieves the current incident identifier from GM_setValue or generates a new one. Data is stored using GM_setValue with a key format of "incident_timeline_" plus the incident ID, ensuring data isolation between incidents. The data structure includes an events array where each event has an id, type, description, notes, and timestamp (stored as milliseconds since epoch). The eventTypes array stores user-customizable event type names. Color mapping is handled through a lookup object (eventColors) that assigns specific hex colors to each event type (e.g., "#ef4444" for Incident Detected, "#60a5fa" for Investigation Started). The renderTimeline() function sorts events chronologically using sort((a,b) => a.timestamp - b.timestamp), then renders each as a flex row with a colored left border, event type badge, description, optional notes, and delete button. Timestamps are formatted using toLocaleString() for human-readable display. The export functions generate formatted text with headers, event count, and each event's timestamp, type, description, and notes, or JSON with the full data structure including eventTypes. All operations are reactive, with automatic persistence and UI updates through saveIncidentData() 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 (events, types, notes, timestamps, and incident identifiers) 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 incident identifier to isolate timelines and never accesses user data, passwords, or sensitive information. Timelines are saved per incident identifier, so ensure you enter a unique identifier for each incident you manage.