Documentation

Reliability & Webhooks

Ensure your integrations stay healthy and your data stays synchronized.

Overview

Reliability is the foundation of Ticket Mate. This section provides the tools and logs needed to monitor the health of your Jira and GitHub connections, and to troubleshoot any issues with incoming webhooks.

Key Features

1. Webhook Logs

Every incoming signal from Jira and GitHub is logged in real-time:

Payload Inspection: View the exact JSON sent by external services.
Processing Status: See if Ticket Mate successfully handled the update.
Retry History: Track automated retries for failed event deliveries.

2. Connection Health

Monitor the heartbeat of your integrations:

OAuth Status: Real-time validation of your Atlassian and GitHub tokens.
Sync Latency: See how long it takes for Jira changes to appear in your dashboard.
Instance Lock Policy: Manage which Jira instances are allowed to communicate with your workspace.

3. Error Diagnostics

When something goes wrong, our diagnostics tools help you find the source:

Common Errors: Detailed explanations for Jira API 401, 403, and 500 errors.
Validation tool: Run a self-check on your environment variables and database connectivity.

Troubleshooting Steps

If Jira changes aren't syncing:

Check the Jira Connection status at the top of the dashboard.
Visit Admin → Reliability → Webhooks to see if events are arriving.
Verify that the Webhook URL in your Jira System Settings matches your Ticket Mate endpoint.

If GitHub PRs aren't linking:

Ensure the repository is connected in Integrations → GitHub.
Check that your branch names or PR titles include the Jira Ticket ID (e.g., TM-123).
Inspect the Webhooks Log for "Push" or "Pull Request" events from GitHub.

Best Practices

Monitor the Log: Check the Webhooks Log after setting up a new automation rule.
Instance Isolation: Only connect the Jira instances needed for your current work to reduce noise.